Hello Brian,
May be I did not understand very well but from what you say I get that
the management server + SQL and NFS are on the same physical hosts that are
being managed by cloudstack?
If those VMs are not visible in Cloudstack, the system is not aware
that they exist so it wont try to roll them to another host if you perform
hypervisor host reboot.
Best regards,
Jordan
-----Original Message-----
From: Brian Fitzpatrick <[email protected]>
Sent: Friday, June 25, 2021 12:06 PM
To: [email protected]
Subject: Management server reboot appears to cause vms on other hosts to
shutdown?
[X] This message came from outside your organization
Hi all,
Still relatively new to CloudStack and learning, testing etc.
I have created 1 management server with mysql on it and created 2 clusters with
a nfs primary storage server in each and a number of hosts in each.
I have been working through the servers, putting them in maintenance mode
(noting the vm migrations), updating and rebooting them. All working fine
I then wanted to update and reboot the server running the management and mysql.
It is also a host, so I set it in maintenance mode so no vms running on it.
I thought if I update it and reboot, all I would lose for a period of time was
access to the management server, the vms should keep running on their various
hosts
The reboot, took longer than usual, it seemed to hang for 15-20mins before
shutting down and rebooting. To my surprise though I lost contact to all the
vms on the other hosts.
They all shut down.
Apologies, if I have missed something here, I thought I understood. All virtual
routers and system vms appeared to be running on the other hosts.
Is it because the management server took a while to reboot, the other hosts
have lost contact and shutdown their vms? seems odd?
Any suggestions, help welcome. As I say, still learning!
Thanks
Brian
