[
https://issues.apache.org/jira/browse/CLOUDSTACK-4040?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sanjeev N updated CLOUDSTACK-4040:
----------------------------------
Attachment: cloud.dmp
management-server.rar
Attached management server log file and cloud DB.
> [Object_store_refactor] System VMs are not spinning up if S3 storage
> configuration is not part of zone creation wizard
> ----------------------------------------------------------------------------------------------------------------------
>
> Key: CLOUDSTACK-4040
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4040
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Storage Controller
> Affects Versions: 4.2.0
> Environment: Latest build from ACS 4.2 branch
> Storage: S3 for secondary and NFS for primary
> Reporter: Sanjeev N
> Priority: Blocker
> Fix For: 4.2.0
>
> Attachments: cloud.dmp, management-server.rar
>
>
> System VMs are not spinning up if S3 storage configuration is not part of
> zone creation wizard. They are coming up only when s3 is added during zone
> creation wizard.
> Steps to Reproduce:
> ================
> 1.Install CS and start MS
> 2.Add secondary storage with S3 as the storage provider before creating the
> zone.
> 3.Create zone with xen cluster and skip adding secondary storage during zone
> creation.
> 4.Add secondary staging storage in the zone created
> 5.Enable zone.
> Expected Result:
> =============
> After zone creation routing template should be downloaded to S3 and after
> adding staging storage system vms spinning up should be initiated.
> Actual Result:
> ===========
> Routing template was not downloaded to S3 after zone creation and system vm
> spinning up not initiated.
> Observations:
> ===========
> 1.After step2 kvm routing template was downloaded to S3 and I could see the
> template info in template_store_ref table.
> 2.After step3 and step4 I expected xen routing template info in
> template_store_ref table. However the entry was not made in the table.
> System vms initiation failed because:"
> Zone host is ready, but console proxy template: 1 is not ready on secondary
> storage.
> "
> 3.Now added another vmware zone and provided s3 storage (with different
> bucket) and secondary staging storage during zone creation and enabled the
> zone.
> 4.Immediately after enabling second zone, xen routing template downloaded to
> S3 and System VMs spinning up got initiated and they came up successfully in
> zone 1. (Even vmware template downloaded to S3 and system vms start up
> initiated )
> Looks like zone to image store mapping is missing if we add image store first
> and zone later. Hence system vms spinning up is failing.
--
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
