cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mice Xia (JIRA)" <>
Subject [jira] [Commented] (CLOUDSTACK-2341) remove network from VM is not removing PF/LB/static nat rules for the VM
Date Wed, 08 May 2013 03:31:16 GMT


Mice Xia commented on CLOUDSTACK-2341:

i suggest only one nic is allowed for a VM in one network, this satisfies most requirements
and has been the assumption for PF/NAT/LB implementation,  e.g. when creating a PF rule CS
will arbitrarily  find a guestNic belonging to the specified network on the target VM. 
And this will simplify the implementation of adding/removing nic to/from VM, otherwise we
have to check if the nic to be removed are associated with any PF/NAT/LB, and if it's not
the last nic in the same network, its related PF/NAT/LB rules need 'migrating' to other nics
in the same network.
> remove network from VM is not removing PF/LB/static nat  rules for the VM
> -------------------------------------------------------------------------
>                 Key: CLOUDSTACK-2341
>                 URL:
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Network Controller
>    Affects Versions: 4.2.0
>         Environment: build:
> CloudStack-non-OSS-MASTER-293-rhel6.3.tar.gz
>            Reporter: shweta agarwal
>            Priority: Blocker
>             Fix For: 4.2.0
> Repro steps:
> 1.Create a VM with network N1
> 2. Create another network N2
> 3. Add N2 to VM created in step 1
> 4. Add PF , Load balancing rules to network N2 for VM
> 5. Acquire an IP in network N2 
> 6. Enable static nat for VM
> 7. Remove network N2 from VM
> Bug:
> PF , Load balancing rules for VM  still exists for the VM in network N2 even though VM
 doesn't belong to network N2 . Even static nat is still active for VM in network N2
> Expected result:
> PF rules , Load balance rules static nat should be  removed for the VM if we remove the
network from the VM .
> To be precise it should be only removed if the removed network is the last nic of that
network in the VM .

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message