cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <>
Subject [jira] [Commented] (CLOUDSTACK-9228) Network update with mistmatch in services require forced option
Date Thu, 21 Apr 2016 08:17:25 GMT


ASF GitHub Bot commented on CLOUDSTACK-9228:

Github user nitin-maharana commented on the pull request:
    @koushik-das: Actually this dialog appears after the first CIDR unchanged confirmation
dialog. If its an admin account, Even if we select yes/no, it will be redirected to second
dialog asking for forced update. According to the input, it will execute the updateNetwork
API with/without forced=true option.
    For user account, It won't be redirected to the second dialog asking for forced update,
it will directly execute updateNetwork API.
    Can you please share some snapshots of what error you are getting.

> Network update with mistmatch in services require forced option
> ---------------------------------------------------------------
>                 Key: CLOUDSTACK-9228
>                 URL:
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>            Reporter: Nitin Kumar Maharana
> 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

This message was sent by Atlassian JIRA

View raw message