GitHub user nitin-maharana opened a pull request:
https://github.com/apache/cloudstack/pull/1333
CLOUDSTACK-9228: Network update with mistmatch in services require forced
option
Steps to reproduce:
===============
1.Bring up CloudStack in advanced zone
2.Create isolated network with sourcenat, pf, lb, firewall services
3.Deploy a VM in the above network
4.Create another network offering with sourcenat, pf, firewall services
5.Try to update the network with offering created in step4
Result:
======
The new offering:DefaultIsolatedNetworkOfferingForVpcNetworksNoLB will
remove the following services [Lb]along with all the related configuration
currently in use. will not proceed with the network update.set forced parameter
to true for forcing an update."
Workaround:
===========
Use api with forced=true
Fix:
===
Added a confirmation dialog box to check whether to make force update or
not.
The dialog appears only for the Admin. Only admin can make force update.
The new dialog appears after the first CIDR unchanged confirmation dialog.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/nitin-maharana/CloudStack
CloudStack-Nitin16_4.7
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/cloudstack/pull/1333.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #1333
----
commit 4b7fef6a68ee2684e3b8c8eb0035f7e36cb1be01
Author: Nitin Kumar Maharana <[email protected]>
Date: 2016-01-01T15:38:20Z
CLOUDSTACK-9228: Network update with mistmatch in services require forced
option
Added a confirmation dialog box to check whether to make force update or
not.
The dialog appears only for the Admin. Only admin can make force update.
The new dialog appears after the first CIDR unchanged confirmation dialog.
----
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
