[
https://issues.apache.org/jira/browse/CLOUDSTACK-9724?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15879529#comment-15879529
]
ASF subversion and git services commented on CLOUDSTACK-9724:
-------------------------------------------------------------
Commit 9efd9059efc1e8d3555fec738668e835a6fc575d in cloudstack's branch
refs/heads/master from [~rajanik]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=9efd905 ]
Merge pull request #1885 from Accelerite/vpctier
CLOUDSTACK-9724: Fixed missing additional public ip on tier network wIn VPC
tier network acquire an ip and configure the PF service on it. VR now will have
the two ip addresses on the interface.
Now restart the VPC tier network with cleanup option. After router comes up the
public interface has only one ip (source nat ip)
Fixed the above issue.
* pr/1885:
CLOUDSTACK-9724: Fixed missing additional public ip on tier network with
cleanup
Signed-off-by: Rajani Karuturi <[email protected]>
> VPC tier network restart with cleanup, missing public ip on VR interface
> ------------------------------------------------------------------------
>
> Key: CLOUDSTACK-9724
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-9724
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Reporter: Jayapal Reddy
> Assignee: Jayapal Reddy
> Fix For: 4.10.0.0
>
>
> On vpc tier network restart with clean up missing secondary ip addresses on
> the VR public interface.
> 1. Create a vpc and deploy a vm in tier.
> 2. Acquire a public ip and configure PF rule
> 3. check that the VR interface has two ip addresses.
> 4. Restart the tier network with cleanup.
> 5. After restart in VR interface ip (PF rule configured) is missed.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
