[
https://issues.apache.org/jira/browse/CLOUDSTACK-5812?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14231229#comment-14231229
]
ASF subversion and git services commented on CLOUDSTACK-5812:
-------------------------------------------------------------
Commit 90d6c01e4078e0d00b9e26498e5d9a85aad8de4a in cloudstack's branch
refs/heads/4.3 from [~alena1108]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=90d6c01 ]
CLOUDSTACK-5812: pass podId information when request for secondary ip address
in Basic zone guest network
(cherry picked from commit 4dcc5671d17bd96feacda0c1999bf1e9a64f530e)
Signed-off-by: Rohit Yadav <[email protected]>
Conflicts:
engine/components-api/src/com/cloud/network/IpAddressManager.java
server/src/com/cloud/network/IpAddressManagerImpl.java
server/src/com/cloud/network/NetworkServiceImpl.java
> 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.3.4#6332)
