[
https://issues.apache.org/jira/browse/CLOUDSTACK-118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13470190#comment-13470190
]
Rohit Yadav commented on CLOUDSTACK-118:
----------------------------------------
@Prashant, this a very special case and most likely your storage or KVM
configuration. I tried to read through the logs but was unable to diagnose the
problem. As you suggest this bug may not be caught everytime, it is may be
time/thread/sync issue.
For KVM, how are disk names set? I see it fails while trying to set uid/gid
over a file that does not exist, and has internal name with patchdisk suffix,
instead of uuid/guid which is the case for Xen.
2012-10-05 12:27:35,585 ERROR [cloud.vm.VirtualMachineManagerImpl]
(HA-Worker-0:work-5) Unable to migrate due to unable to set user and group to
'0:0' on '/mnt/6e8264c6-4591-399b-b4b0-123f61342208/s-1-VM-patchdisk': No such
file or directory
@Sudha: can anyone in BLR/SC be assigned to verify this bug?
Triaging to Edison or anyone on KVM.
Thanks.
> Status of host resorce stuck in "ErrorInMaintenance"
> -----------------------------------------------------
>
> Key: CLOUDSTACK-118
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-118
> Project: CloudStack
> Issue Type: Bug
> Components: Management Server
> Affects Versions: pre-4.0.0
> Environment: XS 6.0.2
> MS Rhl6.3
> Git Revision: 03df2fa9dd45c938f72cd1866044b09d1b0cc978
> Git URL: https://git-wip-us.apache.org/repos/asf/incubator-cloudstack.git
> Reporter: prashant kumar mishra
> Assignee: Abhinandan Prateek
> Priority: Minor
> Fix For: 4.1.0
>
> Attachments: access_log.2012-09-17.txt, access_log.2012-09-26.txt,
> api-server.log, api-server.log, catalina.2012-09-26.log, catalina.out,
> cloud-backup.dmp, management-server.log, management-server.log,
> management-server.log, management-server.log,
> management-server.log.2012-09-16.gz, screenshot-1.jpg, screenshot-2.jpg
>
>
> In a cluster of 2 host if you try to put master in maintenance mode
> ,resource state will be stuck in "ErrorInMaintenance"
> Step to reproduce:
> -----------------------------
> ------------------------------
> 1-Create an advance zone->pod->cluster.
> 2-Add 2 hosts in same cluster.
> 3-Deploy a HA enabled VM .
> 4-put host(one which is pool master ) in maintenance mode .
> Expected result :
> --------------------------
> --------------------------
> status =UP;
> resource status =maintenance
> Actual result:
> ------------------------
> ------------------------
> status=UP;
> resource state=ErrorInMaintenance
--
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
