You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2017/03/01 12:06:45 UTC

[jira] [Commented] (CLOUDSTACK-9779) Releasing secondary guest IP fails with error VM nic Ip x.x.x.x is mapped to load balancing rule

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

ASF GitHub Bot commented on CLOUDSTACK-9779:
--------------------------------------------

Github user SudharmaJain commented on the issue:

    https://github.com/apache/cloudstack/pull/1978
  
    LGTM for the code changes. 


> Releasing secondary guest IP fails with error VM nic Ip x.x.x.x is mapped to load balancing rule
> ------------------------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-9779
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9779
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Management Server
>            Reporter: Nitesh Sarda
>
> ISSUE 
> =================
> Releasing secondary guest IP fails with error VM nic Ip x.x.x.x is mapped to load balancing rule
> REPRO STEPS
> ==================
> 1. Create two isolated guest networks with same CIDR
> 2. Deploy VMs on both networks
> 3. Acquire secondary IP on NICs of both VMs and make sure they have the same value, user can input the IP address.
> 4. Configure Loadbalancing rule on one of the secondary IP address and try releasing the other secondary IP address.
> 5. The operation would fail
> EXPECTED BEHAVIOR
> ==================
> Secondary IP address should be released if there are no LB rules associated with it.
> ACTUAL BEHAVIOR
> ==================
> Releasing secondary IP address even if there are no LB rules associated with it.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)