No need to worry. I'm so much impressed with the quality of oVirt. It has so many different setup scenarios, mine even a tech preview style one ;-)
And good idea to file a bug for usability. To wrap things up: Me typing Luise1 instead of Luise01 was my error to begin with. It triggered everything. Luise01 is our hyper converged oVirt node cluster. It is our ceph bootstrap. Yeah... How could you forget the zero.. node01, node02 and node03 are forming Luise01. I ordered deployment of the engine to node01 on Luise1 and hosted-engine happily did so. Creating a new cluster Luise1 on node01 masking the glusterfs bricks on node01 for the remaining Luise01 cluster nodes. This most probably also triggered this issue: https://lists.ovirt.org/archives/list/[email protected]/thread/L3YCRPRAGPUMBZIBFOPT6L4B7H4M6HLS/ It has already been addressed by Nir Soffer. See https://lists.ovirt.org/archives/list/[email protected]/message/OSZGHT65OUUSGKTLYKJVZPVRFTBPI3EO/ I will create a bug report for that. A node that has already joined a cluster should not be a viable destination for an engine deployment to a new to create cluster. _______________________________________________ Users mailing list -- [email protected] To unsubscribe send an email to [email protected] Privacy Statement: https://www.ovirt.org/site/privacy-policy/ oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/[email protected]/message/YIDVCKVYKRGQUDK4R22Z6GNWRHHZWNMF/
