Mailing-List: contact issues-help@cloudstack.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cloudstack.apache.org
Date: Tue, 7 Jan 2014 01:21:50 +0000 (UTC)
From: "Alena Prokharchyk (JIRA)" <jira@apache.org>
To: cloudstack-issues@incubator.apache.org
Message-ID: <JIRA.12687570.1389057706708.51723.1389057710849@arcas>
In-Reply-To: <JIRA.12687570.1389057706708@arcas>
References: <JIRA.12687570.1389057706708@arcas>
Subject: [jira] [Created] (CLOUDSTACK-5812) Secondary ip allocation in Basic
 zone - the pod is not respected
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Alena Prokharchyk created CLOUDSTACK-5812:
---------------------------------------------

             Summary: Secondary ip allocation in Basic zone - the pod is not respected
                 Key: CLOUDSTACK-5812
                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5812
             Project: CloudStack
          Issue Type: Bug
      Security Level: Public (Anyone can view this level - this is the default.)
    Affects Versions: 4.3.0
            Reporter: Alena Prokharchyk
            Assignee: Alena Prokharchyk
            Priority: Critical
             Fix For: 4.4.0


After reviewing sec ip for nic code, found out that the pod information is not respected when do secondary ip Allocation in Basic zone. We should always pass pod info when request for the new ip, otherwise you might end up with the nic having ips from different pods, which is not acceptable in Basic zone.


--
This message was sent by Atlassian JIRA
(v6.1.5#6160)