cloudstack-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Tamas Monos <tam...@veber.co.uk>
Subject RE: ssvm not re-created after removed
Date Mon, 04 Feb 2013 12:21:56 GMT
Hi,

I do not think there is an easy way to recover from that, unless you restore to 3.0.2 or use
API to deploy an SSVM somehow.
4.0 has a bug that after upgrade for some reason it does not recreate system-vms automatically.
You can find the API reference here: http://incubator.apache.org/cloudstack/docs/api/apidocs-4.0.0/TOC_Root_Admin.html

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

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


-----Original Message-----
From: Andreas Huser [mailto:ahuser@7five-edv.de] 
Sent: 04 February 2013 11:13
To: cloudstack-users@incubator.apache.org
Subject: ssvm not re-created after removed

Hi, 

I have delete manual my secondary storage vm after upgrade from 3.0.2 to 4.0.
And now they will not be created again automatically, what can I do.

In the log files is not something you can use. Only "here is no secondary storage VM for secondary
storage host"
Can we create manual trigger to deploy a new SSVM?

Regards 
Andreas

Mime
View raw message