cloudstack-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Indra Pramana <>
Subject Upgrade failed because system VM was created using old template?
Date Wed, 25 Sep 2013 11:40:48 GMT
Dear all,

I scrutinized the CloudStack management logs during my failed upgrade
attempt from CloudStack 4.1.1 to 4.2.0 and found this on the log:

2013-09-24 02:53:56,029 DEBUG []
(secstorage-1:null) Checking if we need to prepare 1 volumes for
2013-09-24 02:53:56,044 DEBUG [storage.image.TemplateDataFactoryImpl]
(secstorage-1:null) template 3 is already in store:27, type:Image
2013-09-24 02:53:56,069 DEBUG [storage.datastore.PrimaryDataStoreImpl]
(secstorage-1:null) Not found (templateId:3poolId:214) in
template_spool_ref, persisting it
2013-09-24 02:53:56,092 DEBUG [storage.image.TemplateDataFactoryImpl]
(secstorage-1:null) template 3 is already in store:214, type:Primary
2013-09-24 02:53:56,095 DEBUG [storage.volume.VolumeServiceImpl]
(secstorage-1:null) Found template routing-3 in storage pool 214 with
VMTemplateStoragePool id: 76
2013-09-24 02:53:56,105 DEBUG [storage.volume.VolumeServiceImpl]
(secstorage-1:null) Acquire lock on VMTemplateStoragePool 76 with timeout
3600 seconds
2013-09-24 02:53:56,113 INFO  [storage.volume.VolumeServiceImpl]
(secstorage-1:null) lock is acquired for VMTemplateStoragePool 76
2013-09-24 02:53:56,141 DEBUG [storage.motion.AncientDataMotionStrategy]
(secstorage-1:null) copyAsync inspecting src type TEMPLATE copyAsync
inspecting dest type TEMPLATE
2013-09-24 02:53:56,168 DEBUG [agent.transport.Request] (secstorage-1:null)
Seq 37-1888026692: Sending  { Cmd , MgmtId: 161342671900, via: 37, Ver: v1,
Flags: 100111, [

It seems that after the upgrade, the CloudStack management server tries to
create the system VMs using the old template rather than the new 4.2

I did use the wrong filename when registering the template
(systemvm-kvm-4.2.0 instead of systemvm-kvm-4.2) due to wrong information
given by Abhinav but I have since corrected it prior to the upgrade, by
renaming the template name (rather than deleting the template and
re-register it).

My questions:

1. Do I need to get the template name right when I register the
systemvm-kvm-4.2 template from the beginning, prior to the upgrade?

2. Do I need to delete the old system VM template from the template list,
prior to the upgrade? If yes, I think this should be inside the

Looking forward to your reply, thank you.


  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message