Return-Path: X-Original-To: apmail-cloudstack-issues-archive@www.apache.org Delivered-To: apmail-cloudstack-issues-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 1F1F3F382 for ; Tue, 9 Apr 2013 18:26:17 +0000 (UTC) Received: (qmail 9060 invoked by uid 500); 9 Apr 2013 18:26:16 -0000 Delivered-To: apmail-cloudstack-issues-archive@cloudstack.apache.org Received: (qmail 9010 invoked by uid 500); 9 Apr 2013 18:26:16 -0000 Mailing-List: contact issues-help@cloudstack.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cloudstack.apache.org Delivered-To: mailing list issues@cloudstack.apache.org Received: (qmail 8893 invoked by uid 500); 9 Apr 2013 18:26:16 -0000 Delivered-To: apmail-incubator-cloudstack-issues@incubator.apache.org Received: (qmail 8853 invoked by uid 99); 9 Apr 2013 18:26:16 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 09 Apr 2013 18:26:16 +0000 Date: Tue, 9 Apr 2013 18:26:16 +0000 (UTC) From: "Mike Tutkowski (JIRA)" To: cloudstack-issues@incubator.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (CLOUDSTACK-1971) VM deployed to incorrect primary storage MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ 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): > > > > > > > -- 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