[
https://issues.apache.org/jira/browse/CLOUDSTACK-4128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jessica Wang resolved CLOUDSTACK-4128.
--------------------------------------
Resolution: Fixed
> [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,
> jessica_2013_10_25.PNG, management-server.rar, S3-UI.PNG
>
>
> 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 was sent by Atlassian JIRA
(v6.1#6144)
