You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "Sangeetha Hariharan (JIRA)" <ji...@apache.org> on 2013/12/31 02:15:50 UTC

[jira] [Created] (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.

Sangeetha Hariharan created CLOUDSTACK-5685:
-----------------------------------------------

             Summary: [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
             Fix For: 4.3.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.1.5#6160)