You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cloudstack.apache.org by "Abhinandan Prateek (JIRA)" <ji...@apache.org> on 2013/03/01 09:41:15 UTC
[jira] [Commented] (CLOUDSTACK-1411) Issues with VMWare Hypervisor
host_ids not updated when ESX(i) crashes in instance table
[ https://issues.apache.org/jira/browse/CLOUDSTACK-1411?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13590335#comment-13590335 ]
Abhinandan Prateek commented on CLOUDSTACK-1411:
------------------------------------------------
Sateesh,
I guess you fixed it in 4.2, but this issue is there in 4.1.
> Issues with VMWare Hypervisor host_ids not updated when ESX(i) crashes in instance table
> ----------------------------------------------------------------------------------------
>
> Key: CLOUDSTACK-1411
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1411
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the default.)
> Components: Hypervisor Controller
> Affects Versions: 4.0.0, 4.1.0
> Environment: CS 4.0 and 4.1, VMWare vSphere 5.x
> Reporter: ilya musayev
> Assignee: Koushik Das
> Priority: Blocker
> Labels: esxi, hypervisor, vsphere
>
> As noted previously by several users on cloudstack-users mailing list, the host_id are not updated when VM is moved from one hypervisor to another during hypervisor crash. The subsequent tasks that require proper host_id then fail going forward.
> Please reference this thread for more details:
> http://markmail.org/message/byfdmxt3vf2txt5d
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira