[
https://issues.apache.org/jira/browse/CLOUDSTACK-1971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13626448#comment-13626448
]
Srikanteswararao Talluri edited comment on CLOUDSTACK-1971 at 4/9/13 10:20 AM:
-------------------------------------------------------------------------------
This is happening on master too.
I have 3 storage pools added in this order
1. local (created zone with local storage)
2. zone wide
3. cluster wide
Irrespective of the compute offering selected, all the volumes are created on
"cluster wide " storage pool while deploying VM.
was (Author: talluri):
This is happening on master too.
I have 3 storage pools added in this order
1. local (created zone with local storage)
2. zone wide
3. cluster wide
Irrespective of the compute offering selected, all the volumes are created on
"cluster wide " storage pool.
> VM deployed to incorrect primary storage
> ----------------------------------------
>
> Key: CLOUDSTACK-1971
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1971
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Management Server
> Affects Versions: 4.1.0
> Environment: Management Server running on Mac OS X (from source I
> updated and compiled today)
> Reporter: Mike Tutkowski
> Priority: Critical
> Fix For: 4.1.0
>
> Attachments: componentContext.xml.in, nonossComponentContext.xml.in,
> vmops.log, vmops.log
>
>
> From an e-mail to the ClousdStack e-mail list:
> I have three tiers of shared, iSCSI-based storage represented in three
> storage repositories in XenServer:
> SR_2
> SR_3
> SR_4
> SR_2 maps into CS via primary storage PS_2, which has the storage tag PS_2
> SR_3 maps into CS via primary storage PS_3, which has the storage tag PS_3
> SR_4 maps into CS via primary storage PS_4, which has the storage tag PS_4
> I have three compute offerings:
> CO_2, which only uses storage tag PS_2
> CO_3, which only uses storage tag PS_3
> CO_4, which only uses storage tag PS_4
> I walk through the wizard and select CO_3. My VM ends up on SR_4.
> I have double checked the relationships and don't see any errors in how I
> have CS configured.
> Both componentContext.xml.in and nonossComponentContext.xml are configured as
> such (I am running with -Dnonoss, as an FYI):
> <!--
> Storage pool allocators
> -->
> <bean id="LocalStoragePoolAllocator"
> class="com.cloud.storage.allocator.LocalStoragePoolAllocator">
> <property name="name" value="LocalStorage"/>
> </bean>
> <bean id="FirstFitStoragePoolAllocator"
> class="com.cloud.storage.allocator.FirstFitStoragePoolAllocator">
> <property name="name" value="Storage"/>
> </bean>
--
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
