[ https://issues.apache.org/jira/browse/CLOUDSTACK-5426?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14222665#comment-14222665 ]
Rohit Yadav commented on CLOUDSTACK-5426: ----------------------------------------- Thanks for confirming [~prachidamle], do you think it's related to the issue of the failing integration smoke test on 4.3 branch - a test (test_01_sys_vm_start) fails with Simulator as the deployment planner fails to find a storage pool when systemvms are started using simulator. Reference build job - https://travis-ci.org/apache/cloudstack/jobs/41867306 > 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.3.4#6332)