Mailing-List: contact issues-help@cloudstack.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cloudstack.apache.org
Date: Thu, 2 Mar 2017 08:17:45 +0000 (UTC)
From: "ASF GitHub Bot (JIRA)" <jira@apache.org>
To: cloudstack-issues@incubator.apache.org
Message-ID: <JIRA.13041644.1486635065000.40063.1488442665326@Atlassian.JIRA>
In-Reply-To: <JIRA.13041644.1486635065000@Atlassian.JIRA>
References: <JIRA.13041644.1486635065000@Atlassian.JIRA> <JIRA.13041644.1486635065702@jira-lw-us.apache.org>
Subject: [jira] [Commented] (CLOUDSTACK-9779) Releasing secondary guest IP
 fails with error VM nic Ip x.x.x.x is mapped to load balancing rule
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Thu, 02 Mar 2017 08:17:50 -0000


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

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

Github user blueorangutan commented on the issue:

    https://github.com/apache/cloudstack/pull/1978
  
    @borisstoyanov a Jenkins job has been kicked to build packages. I'll keep you posted as I make progress.


> 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)