[jira] [Commented] (CLOUDSTACK-5685) [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.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5685?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14231266#comment-14231266 ] ASF subversion and git services commented on CLOUDSTACK-5685: - Commit b2c240278931c20547482cfd987a4c47f3654609 in cloudstack's branch refs/heads/4.3 from [~kelveny] [ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=b2c2402 ] CLOUDSTACK-5685: reboot VR if a out-of-band power-on event is detected (cherry picked from commit ee2adab7c7c9cf42eaf93c7eedb6dd32ebd8b501) Signed-off-by: Rohit Yadav rohit.ya...@shapeblue.com 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)
[jira] [Commented] (CLOUDSTACK-5685) [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.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5685?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=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 kelv...@gmail.com AuthorDate: Mon Feb 10 16:58:49 2014 -0800 Commit: Rohit Yadav rohit.ya...@shapeblue.com 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 rohit.ya...@shapeblue.com 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)
[jira] [Commented] (CLOUDSTACK-5685) [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.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5685?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14226620#comment-14226620 ] Rohit Yadav commented on CLOUDSTACK-5685: - Hi [~nitinme], is this applicable to 4.3, if you have any idea around this component can you please help backport it to 4.3 branch? Thanks. [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)
[jira] [Commented] (CLOUDSTACK-5685) [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.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5685?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14129408#comment-14129408 ] Nitin Mehta commented on CLOUDSTACK-5685: - Basically the logic is something like this Keleven has made VirtualNetworkApplianceManagerImpl.java (router's Manager) listener to vm's state transitions. So whenever a state transition happens and if it is a VR and old state = stopped and new state = running and the event which triggered is out of band (FollowAgentPowerOnReport) then reboot the router through CS which would result in reprogramming the rules as well. [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)
[jira] [Commented] (CLOUDSTACK-5685) [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.
[ https://issues.apache.org/jira/browse/CLOUDSTACK-5685?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14129406#comment-14129406 ] Nitin Mehta commented on CLOUDSTACK-5685: - commit ee2adab7c7c9cf42eaf93c7eedb6dd32ebd8b501 Author: Kelven Yang kelv...@gmail.com Date: Mon Feb 10 16:58:49 2014 -0800 reboot VR if a out-of-band power-on event is detected [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)
