[
https://issues.apache.org/jira/browse/CLOUDSTACK-7598?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14146216#comment-14146216
]
Devdeep Singh edited comment on CLOUDSTACK-7598 at 9/24/14 11:22 AM:
---------------------------------------------------------------------
As part of commit 7f440854f7bcd41a1bd6581c0239cde2e98261b7, the
directagentattache was updated to retry PingCommand to deal with network
glitches. However, there is a minor bug in the logic because of which the agent
attache is never sending the PingCommand. The vm state is retrieved as part of
this ping command. So if a vm is stopped on the hypervisor, cloudstack will
never update the state of the vms in its db. The retry logic needs to be fixed
to make sure the command is send atleast once.
was (Author: devdeep):
As part of commit 7f440854f7bcd41a1bd6581c0239cde2e98261b7, the
directagentattache was updated to retry PingCommand to deal with network
glitches. However, there is a minor bug in the logic because of which the agent
attache is never sending the PingCommand. The vm state is retrieved as part of
this ping command. So if a vm is stopped on the hypervisor, cloudstack will
never update the state of the vms in its db. The retyr logic needs to be fixed
to make sure the command is send atleast once.
> Cloudstack VM State is not in sync with state from Hypervisor
> -------------------------------------------------------------
>
> Key: CLOUDSTACK-7598
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-7598
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: XenServer
> Affects Versions: 4.5.0
> Reporter: Sailaja Mada
> Assignee: Devdeep Singh
> Priority: Blocker
> Fix For: 4.5.0
>
> Attachments: vmsynclogs.rar
>
>
> Steps:
> 1. Install and configure Adv zone using XS 6.5 Hypervisor
> 2. Deploy Linux VM , Windows VM
> 3. After VM is up and running login to the VM and shutdown the instance
> 4. It moved to Shutdown state in the hypervisor
> 5. But this state is not synced to cloudstack and it remained in running
> state in cloudstack
> Observation:
> Cloudstack VM State is not in sync with state from Hypervisor
> Ob
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
