Mailing-List: contact issues-help@cloudstack.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cloudstack.apache.org
Date: Mon, 23 Sep 2013 20:57:16 +0000 (UTC)
From: "ASF subversion and git services (JIRA)" <jira@apache.org>
To: cloudstack-issues@incubator.apache.org
Message-ID: <JIRA.12662290.1375856037457.4946.1379969836047@arcas>
In-Reply-To: <JIRA.12662290.1375856037457@arcas>
References: <JIRA.12662290.1375856037457@arcas>
Subject: [jira] [Commented] (CLOUDSTACK-4128) [Object_store_Refactor] System
 VMs  start up should check for existence of staging secondary storage in a
 zone
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

ASF subversion and git services commented on CLOUDSTACK-4128:
-------------------------------------------------------------

Commit 3eb899a5ba0b4350e09d3c147762b83291d9f804 in branch refs/heads/4.2-forward from [~jessicawang]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=3eb899a ]

CLOUDSTACK-4128: UI > zone wizard > secondary storage step > provider "S3" > Create NFS staging is required for S3 at this moment. So, disallow user to uncheck "Create NFS Secondary Staging" checkbox when provider is "S3".

                
> [Object_store_Refactor] System VMs  start up should check for existence of staging secondary storage in a zone
> --------------------------------------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-4128
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4128
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: UI
>    Affects Versions: 4.2.0
>         Environment: Latest build from ACS 4.2 Branch
> Storage: S3 for secondary storage
>            Reporter: Sanjeev N
>            Assignee: Jessica Wang
>            Priority: Critical
>             Fix For: 4.2.1
>
>         Attachments: cloud.dmp, jessica_2013_09_12.jpg, jessica_2013_09_17_A.jpg, jessica_2013_09_17_B.jpg, jessica_2013_09_17_C.jpg, jessica_2013_09_17_D.jpg, jessica_2013_09_17_E.jpg, jessica_2013_09_17.sql, management-server.rar
>
>
> System VMs  start up should check for existence of stating secondary storage in a zone.
> With current implementation, adding secondary storage is optional during zone creation wizard. 
> This issue will come in the following scenario:
> ===================================
> 1.Add s3 storage
> 2.Create a zone and skip adding secondary storage during zone creation(Since S3 is already added before zone creation)
> 3.Enable zone
> After enabling the zone CS tries to bring up system vms and will fail since there is no staging secondary storage. After adding staging storage system vms will come up successfully.
> Workaround is at step3 don't enable the zone until we add staging secondary storage. Enable zone after adding staging secondary storage.

--
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