...and of course 30 seconds after I hit send on this message, I find the very obvious line in the documentation about this. I was hoping I could add these new servers to the same cluster and use maintenance mode to migrate the KVM workloads over to the new hosts. Unfor, it appears my only choice is going to be a much more gradual migration and coordinating workload shutdowns, unless anyone has developed a better method?
On Thu, Oct 13, 2022 at 9:52 AM Nux <n...@li.nux.ro> wrote: > Hi, > > Cloudstack tries to keep that demarcation between OSes so as to maintain > some sort of compatibility where software versions and capabilities are > concerned, for stability's sake. > That said, it can be bypassed in code, but it's best to do it like you > have already shown by using another pod. > --- > Nux > www.nux.ro > > On 2022-10-13 15:28, 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. > -- Steve Fuller steveful...@gmail.com
