cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CLOUDSTACK-9228) Network update with mistmatch in services require forced option
Date Mon, 20 Feb 2017 11:58:44 GMT

    [ https://issues.apache.org/jira/browse/CLOUDSTACK-9228?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15874432#comment-15874432
] 

ASF subversion and git services commented on CLOUDSTACK-9228:
-------------------------------------------------------------

Commit c1bc47c10bd0df5cf8a430e00277a375892aad67 in cloudstack's branch refs/heads/master from
[~nitin.maharana]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=c1bc47c ]

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.


> Network update with mistmatch in services require forced option
> ---------------------------------------------------------------
>
>                 Key: CLOUDSTACK-9228
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9228
>             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
(v6.3.15#6346)

Mime
View raw message