cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Min Chen (JIRA)" <>
Subject [jira] [Commented] (CLOUDSTACK-4040) [Object_store_refactor] System VMs are not spinning up if S3 storage configuration is not part of zone creation wizard
Date Sat, 03 Aug 2013 01:14:46 GMT


Min Chen commented on CLOUDSTACK-4040:

Sanjeev, in investigating this blocker defect , we realized a bug introduced back in 3.0.x
in handling dynamically downloading system and built-in templates when a different type of
hypervisor host is added to cloudstack. This used to work in 2.2.x but started to fail since
3.x,  but it seems that QA never report this issue. 

The use case for this is as follows:
1. Create a zone with a host of hypervisor A. System template for A is pre-seeded on secondary
storage, and built-in template will be automatically downloaded to secondary storage when
ssvm is up.
2. Now add another host of hypervisor B into the same zone. 
The expected behavior is that system template and built-in template for hypervisor B should
be downloaded to NFS when the second host is added. 

I want to confirm with you if QA ever tested this scenario. Based on code, it should not work
even back in 3.0.6, 4.0 and 4.1. I didn't recall that I see this in the test plan. If so,
maybe it is worth to add this test in. Since this is the same root cause as CLOUDSTACK-4040
you filed, I checked in a fix a4e256b311519e0cb2dc448bbbcfbd703ffc8219 for it. Would you please
verify this scenario as well in verifying this bug? 
> [Object_store_refactor] System VMs are not spinning up if S3 storage configuration is
not part of zone creation wizard
> ----------------------------------------------------------------------------------------------------------------------
>                 Key: CLOUDSTACK-4040
>                 URL:
>             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
>            Assignee: Min Chen
>            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:

View raw message