You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "jianmoto (JIRA)" <ji...@apache.org> on 2013/09/06 03:35:51 UTC
[jira] [Commented] (CLOUDSTACK-4088) cloudstack will stop and
delete vm which not belongs to cs
[ https://issues.apache.org/jira/browse/CLOUDSTACK-4088?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13759750#comment-13759750 ]
jianmoto commented on CLOUDSTACK-4088:
--------------------------------------
Hi,Abhinandan PrateekThere
You said "There is a way to subvert this by naming a VM using cloudstack naming convention, such VM will not be stopped by CS."
Is that right? Why I do these in my xenserver then the cloudstack stop and remove the vms yet.Is there any details that I ignore?
> cloudstack will stop and delete vm which not belongs to cs
> ----------------------------------------------------------
>
> Key: CLOUDSTACK-4088
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4088
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the default.)
> Components: XenServer
> Affects Versions: 4.0.2, 4.1.0, 4.2.0, Future
> Environment: xenserver 6.0.2
> Reporter: Hongtu Zang
> Labels: removed, vm, xenserver
> Fix For: 4.2.0, Future
>
> Original Estimate: 24h
> Remaining Estimate: 24h
>
> 1.create vm in xenserver, by xencenter
> 2.add xenserver to cloudstack
> the vm will be stopped and removed
> 3.create another vm in xencenter
> it is also removed
--
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