Mailing-List: contact dev-help@cloudstack.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cloudstack.apache.org
From: jayapalu <git@git.apache.org>
To: dev@cloudstack.apache.org
Reply-To: dev@cloudstack.apache.org
References: <git-pr-1450-cloudstack@git.apache.org>
In-Reply-To: <git-pr-1450-cloudstack@git.apache.org>
Subject: [GitHub] cloudstack issue #1450: CLOUDSTACK-9317: Enable/disable static NAT associate...
Content-Type: text/plain
Message-Id: <20170112101850.66147DFA22@git1-us-west.apache.org>
Date: Thu, 12 Jan 2017 10:18:50 +0000 (UTC)
archived-at: Thu, 12 Jan 2017 10:18:52 -0000

Github user jayapalu commented on the issue:

    https://github.com/apache/cloudstack/pull/1450
  
    I tested this patch with below steps. It is not removing the ip addresses on the VR interface. Some times observed that even there is one ip with static nat but the interface got removed.
    
    Steps to test this:
    1. Configure additional public subnet  and acquire 4 ip addresses
    2. Enabled static nat on the 4 public ip addresses.
    3. Go to VR console and see the new public interface created and ips are configured on the interface.
    4. Disable static on all 4 public addresses (disable from UI  one by one quickly)
         expected: inteface should get removed from the VR. But the interface is there in VR
    
    In another case in step4 disable static nat on only 3 public ip addresses. 
    expected: interface with one ip supposed to be there. But the interface is deleted


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---