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: Upgrade 2.2.14 to 4.0.0 : problem with virtual router
Date Thu, 07 Feb 2013 16:19:35 GMT
Hi,

I had the same problem during a 3.0.2->4.0.0 in my test environment.
During upgrade when the new virtual router is being restarted with the new template then a
new VOLUME entry is being created.
So you end up with like:

200 | NULL | 31 | 0 | ROOT-31 | 5e10aa83-828e-4c44-9237-a8d96f358706 | 2097152000 | /Watford/iscsi_0
| ROOT-31 | 1 | 1 | NULL | NULL | ROOT | VMFS | 6 | 8 | NULL | 1 |
201 | NULL | 31 | 0 | ROOT-31 | 0cd93f08-ce1e-4535-a778-744cbed0995f | 2097152000 | /Watford/iscsi_1
| ROOT-31 | 1 | 1 | NULL | NULL | ROOT | VMFS | 6 | 226 | NULL | 1 |

This is BIG problem because as soon as you delete template number 8 the cleanup script will
kill the ROOT-31 volume because it was built on template 8.
To do that CS manager will shut down that VM has ROOT-31 regardless it is now using template
226 and destroys it.

See bug: https://issues.apache.org/jira/browse/CLOUDSTACK-531

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: nicolas.lamirault@orange.com [mailto:nicolas.lamirault@orange.com] 
Sent: 07 February 2013 14:29
To: <cloudstack-users@incubator.apache.org>
Subject: Upgrade 2.2.14 to 4.0.0 : problem with virtual router

hi,

we have upgrade our Cloudstack from version 2.2.14 to 4.0.0, according to http://incubator.apache.org/cloudstack/docs/en-US/Apache_CloudStack/4.0.0-incubating/pdf/Release_Notes/Apache_CloudStack-4.0.0-incubating-Release_Notes-en-US.pdf

The database upgrade works fine. UI too. Then we had launched script
*cloud-sysvmadm* to stop and start system VMs.

The next, all our virtual router were deleted.
Process begins a 7.00 AM.
We can read this command in CS logs : storage.DestroyCommand It's seems to be "cleanup.storage"
process.

In logs, during the upgrade we  have this :

destroy volume-wrapper VM ROOT-xxx

We don't really understand why virtual router and ROOT disks are deleted

Any idea ? Thanks for any help.

Regards


--
Nicolas Lamirault

_________________________________________________________________________________________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees
et ne doivent donc pas etre diffuses, exploites ou copies sans autorisation. Si vous avez
recu ce message par erreur, veuillez le signaler a l'expediteur et le detruire ainsi que les
pieces jointes. Les messages electroniques etant susceptibles d'alteration, France Telecom
- Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged information that may
be protected by law; they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message
and its attachments.
As emails may be altered, France Telecom - Orange is not liable for messages that have been
modified, changed or falsified.
Thank you.




Mime
View raw message