You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@cloudstack.apache.org by "Mice Xia (JIRA)" <ji...@apache.org> on 2013/05/09 05:11:15 UTC

[jira] [Resolved] (CLOUDSTACK-2341) remove network from VM is not removing PF/LB/static nat rules for the VM

     [ https://issues.apache.org/jira/browse/CLOUDSTACK-2341?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Mice Xia resolved CLOUDSTACK-2341.
----------------------------------

    Resolution: Fixed

[fix]
1) only one NIC per network for a VM
2) do not allow the removal of nic if it's used by LB/PF/staticNAT

                
> remove network from VM is not removing PF/LB/static nat  rules for the VM
> -------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-2341
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2341
>             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: http://www.atlassian.com/software/jira