https://www.shapeblue.com/cloudstack-upgrades-best-practices/
i.e. you are interested in parallel upgrade.
i.e. you prepare your Ubuntu 18.04 servers, and later import DB to new
mysql host, install acs 4.13 on new mgmt server etc. Some practice is
needed here.
Read the link I've sent.
Best,
Hi everyone,
We use cloud stack 4.9.2.0 under ubuntu 14.04.
How can I upgrade from cloud stack 4.9.2.0 under ubuntu 14.04 to cloud stack
4.13.0 under ubuntu 1804 ?
Thank you for your help.
System Administrator
Hakan Yıldız
YASAL UYARI: Bu elektronik posta ve onunla iletilen butun
I wouldn't say this is something we do routinely, mostly to correct
mistakes at the start. You could end up with problems if you deployed
VMs based on an old version of a service offering, then changed tags
in such a way that there was no possible location a VM could start up
next time.
However,
Hi Richard,
looks good. Just did an
update network_offerings set service_offering_id = where id =
and restarted one of the networks from this offering with cleanup.
Comes up nicely and new tags are taken into account.
Do you use this procedure in production to change tags and parameters
Great, cheers.
On Wed, 6 Nov 2019 at 08:36, Munjo Jung wrote:
> Hello Andrija,
> Thank you so much for your quick reply. And the issue has been solved.
> The root cause was DB error. There were a storage_pool and its related data
> duplicated on DB.
> after deleting storage pool id, kvm hosts
