[
https://issues.apache.org/jira/browse/CLOUDSTACK-9751?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16104654#comment-16104654
]
ASF subversion and git services commented on CLOUDSTACK-9751:
-------------------------------------------------------------
Commit 0ead11e8f1417f691851dc27341cdaf8b0eb4a4d in cloudstack's branch
refs/heads/4.9 from [~fmaximus]
[ https://gitbox.apache.org/repos/asf?p=cloudstack.git;h=0ead11e ]
CLOUDSTACK-9751: Fix public ip not applied, when added while VR is starting.
(#1925)
Public IP state wasn't passed to the vsp client, making it ignore the apply
public ip.
Reported-By: Raf Smeets <raf.sme...@nuagenetworks.net>
> if a public IP is assigned to a VM when VR is in starting state, it does not
> get applied to the vport in Nuage VSD
> ------------------------------------------------------------------------------------------------------------------
>
> Key: CLOUDSTACK-9751
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9751
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Affects Versions: 4.9.0, 4.10.0.0
> Reporter: Raf Smeets
> Assignee: Frank Maximus
>
> if a public IP is assigned to a VM when VR is in starting state, it does not
> get applied to the vport in Nuage VSD.
> Steps to reproduce:-
> 1) Create a Isolated Network with Dns Network Offering.
> 2) Start a vm in it, it will start a VR
> 3) At this time accquire a Public IP and enable static nat (assigned it to VM
> , Till this time no vport is created for it on the Nuage VSD). No exception
> come cloudstack says successfully.
> 4) After the VM is in running state, the Public Ip in cloudstack is not
> applied to the Nuage VSD.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
