[ 
https://issues.apache.org/jira/browse/CLOUDSTACK-4128?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sanjeev N reopened CLOUDSTACK-4128:
-----------------------------------


Hi Jessica,

As you mentioned in your previous comment, fix would work only if the admin 
followed the order of the steps as you mentioned. 
Assume we don't add S3 storage at step1 and directly go to step2 (which I did 
while verifying the fix) then adding secondary storage wizard will show all the 
supported providers in the provider drop down list. Say we choose S3 at this 
step and unchecked adding staging storage and enabled zone then we hit this 
issue. That is the reason I said the fix would not work for first zone.

Hope this clarified the scenario I tried.

Please let me know if anything is needed.
                
> [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

Reply via email to