[
https://issues.apache.org/jira/browse/CLOUDSTACK-5426?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13843626#comment-13843626
]
ASF subversion and git services commented on CLOUDSTACK-5426:
-------------------------------------------------------------
Commit 6df86db2309db2b93b1001db42b5f797dd445a63 in branch refs/heads/4.3 from
[~prachidamle]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=6df86db ]
CLOUDSTACK-5426: Cannot deploy instance having multiple volumes that use
different storage tags for storage pools in same cluster
Changes:
- We need to reset the avoid set to its original state while calling the
storage pool allocators for each volume.
- This will prevent affecting allocation of the disks due to the avoid set
output of the prior disk allocations.
> Cannot deploy instance having multiple volumes that use different storage
> tags for storage pools in same cluster
> ----------------------------------------------------------------------------------------------------------------
>
> Key: CLOUDSTACK-5426
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5426
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Management Server
> Affects Versions: 4.2.0, 4.2.1, 4.3.0
> Reporter: Prachi Damle
> Assignee: Prachi Damle
> Priority: Critical
> Fix For: 4.3.0
>
>
> This issue can be observed when VM being deployed has multiple volumes (>=2)
> where 2 adjacent volumes are to be created with 2 different disk offerings
> with different storage tags.
> Ex:
> 1. VM1 has 2 volumes root volume & 1 data volume.
> 2. root volume is to be created using a disk offering with storage tag
> 'root_disk'
> 3. data volume is to be created using a disk offering with storage tag
> 'data_disk'
> 4. There exists a cluster wide storage pool suitable for root volume with
> storage tag 'root_disk'
> 5. There exists a cluster wide storage pool suitable for data volume with
> storage tag 'data_disk'
> The deploy VM fails in this case.
--
This message was sent by Atlassian JIRA
(v6.1.4#6159)
