incubator-cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Tamas Monos <tam...@veber.co.uk>
Subject Upgrade 3.0.2->4.0.0
Date Thu, 08 Nov 2012 14:09:39 GMT
Hi,

Sorry putting this on dev-list but got no luck on the user one.

I have upgraded from 3.0.2 to 4.0.0 and the management server started and updated the database
just fine, however the rest of the upgrade procedure just does not work.
I'm running the script: "nohup cloud-sysvmadm -d 192.168.1.5 -u cloud -p password -c -r >
sysvm.log 2>&1 &" accordingly to my environment and see in its log it is trying
to stop/start a router.
It stops it, then recreates the same secondary datastore (vmware) and then starts the same
router rather than deploying the new imported systemVM template and creating a new one.
It neither touches the sec-storage VM nor the console-proxy VM so new management system, old
systemVMs.

No errors during running the script no errors in the log:
Stopping and starting 1 running routing vm(s)...
Done restarting router(s).

Is there a way to bypass this and convince CS 4.0 manually to use the new imported systemvm-vmware-3.0.5
template for systemvms?
This way I could just destroy the systemvms and CS would re-create them with the new template.

Thanks in advance.

Regards

Tamas Monos                                               DDI         +44(0)2034687012
Chief Technical                                             Office    +44(0)2034687000
Veber: The Hosting Specialists               Fax         +44(0)871 522 7057
http://www.veber.co.uk<http://www.veber.co.uk/>

Follow us on Twitter: www.twitter.com/veberhost<http://www.twitter.com/veberhost>
Follow us on Facebook: www.facebook.com/veberhost<http://www.facebook.com/veberhost>


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