I just stood up a Ubuntu cluster and started adding hosts to it while
decommissioning hosts from the Centos cluster and restarting virtual
machines onto it. The whole point of a cluster is that it is homogeneous
so that things like virtual machine migration can be assured to work.
There's no way that Centos and Ubuntu are going to have identical KVM
versions guaranteed to make things like virtual machine migration work,
nevermind all the other environmental stuff that needs to be identical
in order to make virtual machine migration actually work.
In short, you can do it using the workarounds others have provided, but
the more reliable way is to stand up a new cluster with the new OS and
manually shut down VM's and then start them up on the new cluster.
Painful if you don't have the compute resources to do the move all in
one service outage, but (shrug). It's the reliable way to do things.
On 10/13/2022 7:28 AM, S.Fuller wrote:
I am working to transition the host OS for my Cloudstack 4.11.3 hosts from
CentOS to Ubuntu. I was able successfully bring up a new Ubuntu host with
Cloudstack and wanted to have it be part of an existing cluster, but after
attempting to add the server I'm noting the following warning in the agent
log file
"Can't add host: XX.XX.XX.XX with hostOS: Ubuntu into a cluster,in which
there are CentOS hosts added"
Is this really the case? I did not see anything obvious in the
documentation about this. I was able to successfully add the new Ubuntu
server into a new cluster within the same POD, and have it see storage,
networking, etc, so the host itself appears to be configured correctly.
