[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-7598?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14147528#comment-14147528
 ] 

ASF subversion and git services commented on CLOUDSTACK-7598:
-------------------------------------------------------------

Commit 55b4ead49594212ba55bfcf7007b0cae11bf68ba in cloudstack's branch 
refs/heads/master from [~devdeep]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=55b4ead ]

CLOUDSTACK-7598: When a vm deployed by cloudstack is stopped on the hypervisor
(outside cloudstack), the state of the vm is not updated in cloudstack db. The
ping task was not checking for resource (host) status by default. The power
state of the vms is returned as part of the resource status. Fixed the issue by
making sure ping task atleast tries once to get the resource status.


> 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)

Reply via email to