[
https://issues.apache.org/jira/browse/CLOUDSTACK-10061?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16151033#comment-16151033
]
ASF subversion and git services commented on CLOUDSTACK-10061:
--------------------------------------------------------------
Commit f5cebeb71af1ce097c20fd4d3b3ba6f31e28cbfd in cloudstack's branch
refs/heads/master from [~syed1]
[ https://gitbox.apache.org/repos/asf?p=cloudstack.git;h=f5cebeb ]
CLOUDSTACK-10061: When starting a VM, make sure it is attached to correct VAG
when using managed storage (#2253)
This can happen when you stop a VM in one cluster and start a VM in another
cluster. When the VM starts in a new cluster, we don't add a new VAG and hence
it fails to start. This PR ensures that we call grantAccess to the VM that gets
started which will fix the access issue.
> When starting a VM, make sure it has the correct volume access group
> --------------------------------------------------------------------
>
> Key: CLOUDSTACK-10061
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10061
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Storage Controller
> Affects Versions: Future
> Reporter: Syed Ahmed
> Fix For: Future
>
>
> This can happen when you stop a VM in one cluster and start a VM in another
> cluster. When the VM starts in a new cluster, we don't add a new VAG and
> hence it fails to start. This PR ensures that we call grantAccess to the VM
> that gets started which will fix the access issue.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
