[
https://issues.apache.org/jira/browse/CLOUDSTACK-4128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jessica Wang resolved CLOUDSTACK-4128.
--------------------------------------
Resolution: Cannot Reproduce
Sanjeev,
My fix at 12/Sep/13 works for the first zone, too.
The screenshot(jessica_2013_09_12.jpg) I provided at 12/Sep/13 came from zone
creation of the first zone (i.e. before the first zone was created).
Here is my steps:
(1) Infrastructure > Secondary Storage > Add Secondary Stoarge
=> select Provider as S3, uncheck "Create NFS Secondary Staging Store"
(as my attachment "jessica_2013_09_17_A.jpg", "jessica_2013_09_17_B.jpg",
"jessica_2013_09_17_C.jpg")
(2) Infrastructure > Zones > Add Zone > Secondary Storage step
=> as my attachment "jessica_2013_09_17_D.jpg",
When clicking Provider dropdown, the dropdown shows only one option "S3" (no
blank option), as my attachment "jessica_2013_09_17_E.jpg".
Therefore, staging secondary storage in Add Zone wizard is required (not
optional) as long as S3 storage exists.
(as you can see in "jessica_2013_09_17_D.jpg", "jessica_2013_09_17_E.jpg" that
"NFS Server", "Path" are required fields.)
I attached my database dump "jessica_2013_09_17.sql" (which has S3 storage, but
no zone).
Please try to restore my database dump on your machine and you will see
Provider dropdown has only one option "S3"(no blank option) and staging
secondary storage in Add Zone wizard is required in zone creation of the first
zone.
If you see something different (i.e. Provider dropdown has more than one option
or staging secondary storage in Add Zone wizard is NOT required), please attach
screenshot.
Jessica
> [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
