[
https://issues.apache.org/jira/browse/CLOUDSTACK-5685?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14231269#comment-14231269
]
Rohit Yadav commented on CLOUDSTACK-5685:
-----------------------------------------
Already fixed in 4.4, 4.5, master branches.
backported to 4.3;
commit b2c240278931c20547482cfd987a4c47f3654609
Refs: 4.3.0-413-gb2c2402
Author: Kelven Yang <[email protected]>
AuthorDate: Mon Feb 10 16:58:49 2014 -0800
Commit: Rohit Yadav <[email protected]>
CommitDate: Tue Dec 2 15:30:24 2014 +0530
CLOUDSTACK-5685: reboot VR if a out-of-band power-on event is detected
(cherry picked from commit ee2adab7c7c9cf42eaf93c7eedb6dd32ebd8b501)
Signed-off-by: Rohit Yadav <[email protected]>
Conflicts:
server/src/com/cloud/network/router/VirtualNetworkApplianceManagerImpl.java
> [Vmsync] - When VR is rebooted outside of cloudstack , there is no change in
> state detected by cloudstack resulting in VR not bieng programmed with any
> rules.
> --------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: CLOUDSTACK-5685
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5685
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Management Server
> Affects Versions: 4.3.0
> Environment: Build from 4.3
> Reporter: Sangeetha Hariharan
> Assignee: Kelven Yang
> Fix For: 4.4.0
>
>
> [Vmsync] - When VR is rebooted outside of cloudstack , there is no change in
> state detected by cloudstack resulting in VR not being programmed with any
> rules.
> PreReq:
> Have few Vms deployed using Cloudstack.
> Have PF,Static NAT,LB and Egress rules programmed for the Vms.
> Steps:
> Outside of Cloudstack, Reboot VR.
> After the successful reboot of VR , there are no rules being programmed in
> the VR for the Vms.
> Currently , VM sync does not detect any change of state in the router when
> router is rebooted. So there is no way for CS to know that the router needs
> to be reprogrammed.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
