[
https://issues.apache.org/jira/browse/CLOUDSTACK-4088?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13729604#comment-13729604
]
Hongtu Zang edited comment on CLOUDSTACK-4088 at 8/5/13 4:14 PM:
-----------------------------------------------------------------
I don't think it is reasonable.
I saw cs will skip stopping vm which is not following the naming of CS in the
fullSync function.
so, I think it should skip stopping vm in deltaSync also. If it is by design,
why the code do not stop it in fullSync?
was (Author: hongtu_zang):
I don't think it is reasonable.
I saw cs will skip stopping vm which is not following the naming of CS in the
fullSync function.
so, I think it should skip stopping vm in deltaSync also. If it is by design,
why the code won't stop it in fullSync?
> 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
