cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mike Tutkowski (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CLOUDSTACK-1971) VM deployed to incorrect primary storage
Date Tue, 09 Apr 2013 18:26:16 GMT

    [ https://issues.apache.org/jira/browse/CLOUDSTACK-1971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13626915#comment-13626915
] 

Mike Tutkowski commented on CLOUDSTACK-1971:
--------------------------------------------

Hi Prachi,

I am new to Git, so it is entirely possible I'm doing something wrong there.

I ran a "git fetch upstream" where "upstream" is defined as the following:

upstream	https://github.com/apache/incubator-cloudstack.git (fetch)

I then did a "git merge upstream/4.1" while on my local 4.1 branch and received the following
message:

Already up-to-date.

Is it possible my upstream repo is not the latest?

Thanks!
                
> 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
>            Assignee: Prachi Damle
>            Priority: Critical
>             Fix For: 4.1.0
>
>         Attachments: applicationContext.xml.in, 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

Mime
View raw message