cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Guillaume Fraysse (JIRA)" <>
Subject [jira] [Commented] (CLOUDSTACK-531) Potential disaster with template-cleanup enabled!
Date Fri, 08 Feb 2013 07:11:13 GMT


Guillaume Fraysse commented on CLOUDSTACK-531:

We encountered the same issue while upgrading from 2.2.13 to 4.0, this sounds like a dupe
of this issue :

It should have been fixed in 4.0.1
> Potential disaster with template-cleanup enabled!
> -------------------------------------------------
>                 Key: CLOUDSTACK-531
>                 URL:
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Template
>    Affects Versions: 4.0.0
>            Reporter: Tamas Monos
>            Priority: Blocker
> Hi,
> I've done an upgrade from 3.0.2 -> 4.0.0.
> All went OK with some workarounds:
> 1. Add new vmware template to CS with name systemvm-vmware-4.0 (I have re-imported it)
> 2. Wait till the template is downloaded and installed successfully
> 3. Look up id of this template in DB (Name should match the input provided in step
> mysql> select id from `cloud`.`vm_template` where name = 
> mysql> 'systemvm-vmware-4.0' and removed is null;
> 4. Update template type to SYSTEM
> mysql> update `cloud`.`vm_template` set type='SYSTEM' where id = 
> mysql> <id-from-step3>;
> 5. Update template Id for all system Vms
> mysql> update `cloud`.`vm_instance` set vm_template_id = <id-from-step3> 
> mysql> where type <> 'User' and hypervisor_type = 'VMware';
> I was very happy as the platform was just working fine. Then I've enabled "storage.template.cleanup.enabled".
This resulted in destruction of my running(!!!) systemVMs.
> Then the management server started telling me that the Zone is not ready for secondary
> I tried to add a new one which failed. I've removed the current one and tried to recreate
it, failed.
> Management server logs will follow shortly.

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