Hello all, I'm more-or-less finished building a new ovirt over glusterfs cluster with 3 fairly beefy servers. Nodes were fully upgraded to CentOS Linux release 8.3.2011 before they joined the cluster. Looking at the cluster view in the WebUI, I get an exclamation mark with the following message: "Upgrade cluster compatibility level". When I try to upgrade the cluster, 2 of the 3 hosts go into maintenance and reboot, but once the procedure is complete, the cluster version remains the same. Looking at the host vdsm logs, I see that once the engine refreshes their capabilities, all hosts return 4.2-4.4 and not 4.5. E.g. 'supportedENGINEs': ['4.2', '4.3', '4.4'], 'clusterLevels': ['4.2', '4.3', '4.4'] I assume I should be seeing 4.5 after the upgrade, no? AmI missing something? Thanks, - Gilboa _______________________________________________ Users mailing list -- users(a)ovirt.org To unsubscribe send an email to users-leave(a)ovirt.org Privacy Statement: https://www.ovirt.org/privacy-policy.html oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/7CCUHPEGVZD...

Shani, 1. I created a new 4.5 cluster with the same CPU (Secure Intel Cascadelake Server Family) and platform type (Q35/BIOS). 2. All 3 hosts are 8.3, but report 4.4 compatibility. 3. The only reason I attempted to upgrade the cluster was simple: The cluster state kept on dropping down to "unavailable" (even though all 3 hosts are up) and I was offered to upgrade the cluster to v4.5. - Gilboa On Wed, Dec 16, 2020 at 1:28 PM Shani Leviim <sleviim(a)redhat.com&gt; wrote: > Hi Gilboa, > > Here are some guidelines/checks: > - Are you able to create a 4.5 DC/cluster? > - Host can be Up in the 4.5 clusters only when it reports 4.5 level > compatibility (it's based on RHEL 8.3). > Can you make sure that on all 3 hosts? > - You can upgrade the 4.4 clusters to 4.5 only when all Up/NonOperational > hosts are reporting 4.5 level > - You can upgrade 4.4 DC to 4.5 only when all clusters inside are on the > 4.5 level > - A 4.5 host-based on RHEL 8.3 should be fully functional in 4.2/4.3/4.4 > clusters > > > > *Regards,* > > *Shani Leviim* > > > On Wed, Dec 16, 2020 at 12:53 PM Gilboa Davara <gilboad(a)gmail.com&gt; wrote: > >> Hello all, >> >> I'm more-or-less finished building a new ovirt over glusterfs cluster >> with 3 fairly beefy servers. >> Nodes were fully upgraded to CentOS Linux release 8.3.2011 before they >> joined the cluster. >> Looking at the cluster view in the WebUI, I get an exclamation mark with >> the following message: "Upgrade cluster compatibility level". >> When I try to upgrade the cluster, 2 of the 3 hosts go into maintenance >> and reboot, but once the procedure is complete, the cluster version remains >> the same. >> Looking at the host vdsm logs, I see that once the engine refreshes >> their capabilities, all hosts return 4.2-4.4 and not 4.5. >> >> E.g. >> 'supportedENGINEs': ['4.2', '4.3', '4.4'], 'clusterLevels': ['4.2', >> '4.3', '4.4'] >> I assume I should be seeing 4.5 after the upgrade, no? >> >> AmI missing something? >> >

>> Thanks, >> - Gilboa >> _______________________________________________ >> Users mailing list -- users(a)ovirt.org >> To unsubscribe send an email to users-leave(a)ovirt.org >> Privacy Statement: https://www.ovirt.org/privacy-policy.html >> oVirt Code of Conduct: >> https://www.ovirt.org/community/about/community-guidelines/ >> List Archives: >> https://lists.ovirt.org/archives/list/users@ovirt.org/message/7CCUHPEGVZD... >> > _______________________________________________ Users mailing list -- users(a)ovirt.org To unsubscribe send an email to users-leave(a)ovirt.org Privacy Statement: https://www.ovirt.org/privacy-policy.html oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/RMZ3S64FFIO...

Thanks for the prompt reply. I assume I can safely ignore the "Upgrade cluster compatibility" warning until libvirt 6.6 gets pushed to CentOS 8.3?

- Gilboa On Wed, Dec 16, 2020 at 5:56 PM Martin Perina <mperina(a)redhat.com&gt; wrote: > > > On Wed, Dec 16, 2020 at 2:25 PM Gilboa Davara <gilboad(a)gmail.com&gt; wrote: > >> Shani, >> >> 1. I created a new 4.5 cluster with the same CPU (Secure Intel >> Cascadelake Server Family) and platform type (Q35/BIOS). >> 2. All 3 hosts are 8.3, but report 4.4 compatibility. >> 3. The only reason I attempted to upgrade the cluster was simple: The >> cluster state kept on dropping down to "unavailable" (even though all 3 >> hosts are up) and I was offered to upgrade the cluster to v4.5. >> >> - Gilboa >> >> On Wed, Dec 16, 2020 at 1:28 PM Shani Leviim <sleviim(a)redhat.com&gt; wrote: >> >>> Hi Gilboa, >>> >>> Here are some guidelines/checks: >>> - Are you able to create a 4.5 DC/cluster? >>> - Host can be Up in the 4.5 clusters only when it reports 4.5 level >>> compatibility (it's based on RHEL 8.3). >>> Can you make sure that on all 3 hosts? >>> - You can upgrade the 4.4 clusters to 4.5 only when all >>> Up/NonOperational hosts are reporting 4.5 level >>> - You can upgrade 4.4 DC to 4.5 only when all clusters inside are on >>> the 4.5 level >>> - A 4.5 host-based on RHEL 8.3 should be fully functional in >>> 4.2/4.3/4.4 clusters >>> >>> >>> >>> *Regards,* >>> >>> *Shani Leviim* >>> >>> >>> On Wed, Dec 16, 2020 at 12:53 PM Gilboa Davara <gilboad(a)gmail.com&gt; >>> wrote: >>> >>>> Hello all, >>>> >>>> I'm more-or-less finished building a new ovirt over glusterfs cluster >>>> with 3 fairly beefy servers. >>>> Nodes were fully upgraded to CentOS Linux release 8.3.2011 before they >>>> joined the cluster. >>>> Looking at the cluster view in the WebUI, I get an exclamation mark >>>> with the following message: "Upgrade cluster compatibility level". >>>> When I try to upgrade the cluster, 2 of the 3 hosts go into >>>> maintenance and reboot, but once the procedure is complete, the cluster >>>> version remains the same. >>>> Looking at the host vdsm logs, I see that once the engine refreshes >>>> their capabilities, all hosts return 4.2-4.4 and not 4.5. >>>> >>>> E.g. >>>> 'supportedENGINEs': ['4.2', '4.3', '4.4'], 'clusterLevels': ['4.2', >>>> '4.3', '4.4'] >>>> I assume I should be seeing 4.5 after the upgrade, no? >>>> >>>> AmI missing something? >>>> >>> > EL 8.3 is not enough, you also need Advanced Virtualization 8.3 (in > particular libvirt 6.6) > >> >>>> Thanks, >>>> - Gilboa >>>> _______________________________________________ >>>> Users mailing list -- users(a)ovirt.org >>>> To unsubscribe send an email to users-leave(a)ovirt.org >>>> Privacy Statement: https://www.ovirt.org/privacy-policy.html >>>> oVirt Code of Conduct: >>>> https://www.ovirt.org/community/about/community-guidelines/ >>>> List Archives: >>>> https://lists.ovirt.org/archives/list/users@ovirt.org/message/7CCUHPEGVZD... >>>> >>> _______________________________________________ >> Users mailing list -- users(a)ovirt.org >> To unsubscribe send an email to users-leave(a)ovirt.org >> Privacy Statement: https://www.ovirt.org/privacy-policy.html >> oVirt Code of Conduct: >> https://www.ovirt.org/community/about/community-guidelines/ >> List Archives: >> https://lists.ovirt.org/archives/list/users@ovirt.org/message/RMZ3S64FFIO... >> > > > -- > Martin Perina > Manager, Software Engineering > Red Hat Czech s.r.o. >

On Wed, Dec 16, 2020 at 6:21 PM Martin Perina <mperina(a)redhat.com&gt; wrote: > > > On Wed, Dec 16, 2020 at 4:59 PM Gilboa Davara <gilboad(a)gmail.com&gt; wrote: > >> Thanks for the prompt reply. >> I assume I can safely ignore the "Upgrade cluster compatibility" warning >> until libvirt 6.6 gets pushed to CentOS 8.3? >> > > We are working on releasing AV 8.3, hopefully it will be available soon, > but until that happen you have no way how to upgrade to CL 4.5 and you just > need to stay in 4.4 > Understood. Thanks again. - Gilboa

>> - Gilboa >> >> On Wed, Dec 16, 2020 at 5:56 PM Martin Perina <mperina(a)redhat.com&gt; >> wrote: >> >>> >>> >>> On Wed, Dec 16, 2020 at 2:25 PM Gilboa Davara <gilboad(a)gmail.com&gt; >>> wrote: >>> >>>> Shani, >>>> >>>> 1. I created a new 4.5 cluster with the same CPU (Secure Intel >>>> Cascadelake Server Family) and platform type (Q35/BIOS). >>>> 2. All 3 hosts are 8.3, but report 4.4 compatibility. >>>> 3. The only reason I attempted to upgrade the cluster was simple: The >>>> cluster state kept on dropping down to "unavailable" (even though all 3 >>>> hosts are up) and I was offered to upgrade the cluster to v4.5. >>>> >>>> - Gilboa >>>> >>>> On Wed, Dec 16, 2020 at 1:28 PM Shani Leviim <sleviim(a)redhat.com&gt; >>>> wrote: >>>> >>>>> Hi Gilboa, >>>>> >>>>> Here are some guidelines/checks: >>>>> - Are you able to create a 4.5 DC/cluster? >>>>> - Host can be Up in the 4.5 clusters only when it reports 4.5 level >>>>> compatibility (it's based on RHEL 8.3). >>>>> Can you make sure that on all 3 hosts? >>>>> - You can upgrade the 4.4 clusters to 4.5 only when all >>>>> Up/NonOperational hosts are reporting 4.5 level >>>>> - You can upgrade 4.4 DC to 4.5 only when all clusters inside are on >>>>> the 4.5 level >>>>> - A 4.5 host-based on RHEL 8.3 should be fully functional in >>>>> 4.2/4.3/4.4 clusters >>>>> >>>>> >>>>> >>>>> *Regards,* >>>>> >>>>> *Shani Leviim* >>>>> >>>>> >>>>> On Wed, Dec 16, 2020 at 12:53 PM Gilboa Davara <gilboad(a)gmail.com&gt; >>>>> wrote: >>>>> >>>>>> Hello all, >>>>>> >>>>>> I'm more-or-less finished building a new ovirt over glusterfs >>>>>> cluster with 3 fairly beefy servers. >>>>>> Nodes were fully upgraded to CentOS Linux release 8.3.2011 before >>>>>> they joined the cluster. >>>>>> Looking at the cluster view in the WebUI, I get an exclamation mark >>>>>> with the following message: "Upgrade cluster compatibility level". >>>>>> When I try to upgrade the cluster, 2 of the 3 hosts go into >>>>>> maintenance and reboot, but once the procedure is complete, the cluster >>>>>> version remains the same. >>>>>> Looking at the host vdsm logs, I see that once the engine refreshes >>>>>> their capabilities, all hosts return 4.2-4.4 and not 4.5. >>>>>> >>>>>> E.g. >>>>>> 'supportedENGINEs': ['4.2', '4.3', '4.4'], 'clusterLevels': ['4.2', >>>>>> '4.3', '4.4'] >>>>>> I assume I should be seeing 4.5 after the upgrade, no? >>>>>> >>>>>> AmI missing something? >>>>>> >>>>> >>> EL 8.3 is not enough, you also need Advanced Virtualization 8.3 (in >>> particular libvirt 6.6) >>> >>>> >>>>>> Thanks, >>>>>> - Gilboa >>>>>> _______________________________________________ >>>>>> Users mailing list -- users(a)ovirt.org >>>>>> To unsubscribe send an email to users-leave(a)ovirt.org >>>>>> Privacy Statement: https://www.ovirt.org/privacy-policy.html >>>>>> oVirt Code of Conduct: >>>>>> https://www.ovirt.org/community/about/community-guidelines/ >>>>>> List Archives: >>>>>> https://lists.ovirt.org/archives/list/users@ovirt.org/message/7CCUHPEGVZD... >>>>>> >>>>> _______________________________________________ >>>> Users mailing list -- users(a)ovirt.org >>>> To unsubscribe send an email to users-leave(a)ovirt.org >>>> Privacy Statement: https://www.ovirt.org/privacy-policy.html >>>> oVirt Code of Conduct: >>>> https://www.ovirt.org/community/about/community-guidelines/ >>>> List Archives: >>>> https://lists.ovirt.org/archives/list/users@ovirt.org/message/RMZ3S64FFIO... >>>> >>> >>> >>> -- >>> Martin Perina >>> Manager, Software Engineering >>> Red Hat Czech s.r.o. >>> >> > > -- > Martin Perina > Manager, Software Engineering > Red Hat Czech s.r.o. > _______________________________________________ Users mailing list -- users(a)ovirt.org To unsubscribe send an email to users-leave(a)ovirt.org Privacy Statement: https://www.ovirt.org/privacy-policy.html oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/OEL5Y7UYBGL...

On Tue, Dec 22, 2020 at 11:45 AM Sandro Bonazzola <sbonazzo(a)redhat.com&gt; wrote: > > > Il giorno mer 16 dic 2020 alle ore 17:43 Gilboa Davara <gilboad(a)gmail.com&gt; > ha scritto: > >> On Wed, Dec 16, 2020 at 6:21 PM Martin Perina <mperina(a)redhat.com&gt; >> wrote: >> >>> >>> >>> On Wed, Dec 16, 2020 at 4:59 PM Gilboa Davara <gilboad(a)gmail.com&gt; >>> wrote: >>> >>>> Thanks for the prompt reply. >>>> I assume I can safely ignore the "Upgrade cluster compatibility" >>>> warning until libvirt 6.6 gets pushed to CentOS 8.3? >>>> >>> >>> We are working on releasing AV 8.3, hopefully it will be available >>> soon, but until that happen you have no way how to upgrade to CL 4.5 and >>> you just need to stay in 4.4 >>> >> >> Understood. >> >> Thanks again. >> - Gilboa >> >> > > Just updating that oVirt 4.4.4 released yesterday comes with Advanced > Virtualization 8.3 so you can now enable CL 4.5. > Sadly enough, even post-full-upgrade (engine + hosts) something seems to be broken. In the WebUI, I see all 3 hosts marked as "up". But when I run hosted-engine --vm-status (or migrate the hosted engine), only the first (original deployed) host is available. I tried "reinstalling" (from the WebUI) the two hosts, no errors, no change. I tried upgrading the cluster again, host 2 / 3 (the "missing" hosts) upgrade is successful; hosts1 fails (cannot migrate the hosted engine). Any idea what's broken? - Gilboa

> > >> >>>> - Gilboa >>>> >>>> On Wed, Dec 16, 2020 at 5:56 PM Martin Perina <mperina(a)redhat.com&gt; >>>> wrote: >>>> >>>>> >>>>> >>>>> On Wed, Dec 16, 2020 at 2:25 PM Gilboa Davara <gilboad(a)gmail.com&gt; >>>>> wrote: >>>>> >>>>>> Shani, >>>>>> >>>>>> 1. I created a new 4.5 cluster with the same CPU (Secure Intel >>>>>> Cascadelake Server Family) and platform type (Q35/BIOS). >>>>>> 2. All 3 hosts are 8.3, but report 4.4 compatibility. >>>>>> 3. The only reason I attempted to upgrade the cluster was simple: >>>>>> The cluster state kept on dropping down to "unavailable" (even though all 3 >>>>>> hosts are up) and I was offered to upgrade the cluster to v4.5. >>>>>> >>>>>> - Gilboa >>>>>> >>>>>> On Wed, Dec 16, 2020 at 1:28 PM Shani Leviim <sleviim(a)redhat.com&gt; >>>>>> wrote: >>>>>> >>>>>>> Hi Gilboa, >>>>>>> >>>>>>> Here are some guidelines/checks: >>>>>>> - Are you able to create a 4.5 DC/cluster? >>>>>>> - Host can be Up in the 4.5 clusters only when it reports 4.5 level >>>>>>> compatibility (it's based on RHEL 8.3). >>>>>>> Can you make sure that on all 3 hosts? >>>>>>> - You can upgrade the 4.4 clusters to 4.5 only when all >>>>>>> Up/NonOperational hosts are reporting 4.5 level >>>>>>> - You can upgrade 4.4 DC to 4.5 only when all clusters inside are >>>>>>> on the 4.5 level >>>>>>> - A 4.5 host-based on RHEL 8.3 should be fully functional in >>>>>>> 4.2/4.3/4.4 clusters >>>>>>> >>>>>>> >>>>>>> >>>>>>> *Regards,* >>>>>>> >>>>>>> *Shani Leviim* >>>>>>> >>>>>>> >>>>>>> On Wed, Dec 16, 2020 at 12:53 PM Gilboa Davara <gilboad(a)gmail.com&gt; >>>>>>> wrote: >>>>>>> >>>>>>>> Hello all, >>>>>>>> >>>>>>>> I'm more-or-less finished building a new ovirt over glusterfs >>>>>>>> cluster with 3 fairly beefy servers. >>>>>>>> Nodes were fully upgraded to CentOS Linux release 8.3.2011 before >>>>>>>> they joined the cluster. >>>>>>>> Looking at the cluster view in the WebUI, I get an exclamation >>>>>>>> mark with the following message: "Upgrade cluster compatibility level". >>>>>>>> When I try to upgrade the cluster, 2 of the 3 hosts go into >>>>>>>> maintenance and reboot, but once the procedure is complete, the cluster >>>>>>>> version remains the same. >>>>>>>> Looking at the host vdsm logs, I see that once the engine >>>>>>>> refreshes their capabilities, all hosts return 4.2-4.4 and not 4.5. >>>>>>>> >>>>>>>> E.g. >>>>>>>> 'supportedENGINEs': ['4.2', '4.3', '4.4'], 'clusterLevels': >>>>>>>> ['4.2', '4.3', '4.4'] >>>>>>>> I assume I should be seeing 4.5 after the upgrade, no? >>>>>>>> >>>>>>>> AmI missing something? >>>>>>>> >>>>>>> >>>>> EL 8.3 is not enough, you also need Advanced Virtualization 8.3 (in >>>>> particular libvirt 6.6) >>>>> >>>>>> >>>>>>>> Thanks, >>>>>>>> - Gilboa >>>>>>>> _______________________________________________ >>>>>>> >>>>>>> > > >

On Wed, Dec 23, 2020 at 6:28 PM Gilboa Davara <gilboad(a)gmail.com&gt; wrote: > > > On Wed, Dec 23, 2020 at 6:20 PM Gilboa Davara <gilboad(a)gmail.com&gt; wrote: > >> On Tue, Dec 22, 2020 at 11:45 AM Sandro Bonazzola <sbonazzo(a)redhat.com&gt; >> wrote: >> >>> >>> >>> Il giorno mer 16 dic 2020 alle ore 17:43 Gilboa Davara < >>> gilboad(a)gmail.com&gt; ha scritto: >>> >>>> On Wed, Dec 16, 2020 at 6:21 PM Martin Perina <mperina(a)redhat.com&gt; >>>> wrote: >>>> >>>>> >>>>> >>>>> On Wed, Dec 16, 2020 at 4:59 PM Gilboa Davara <gilboad(a)gmail.com&gt; >>>>> wrote: >>>>> >>>>>> Thanks for the prompt reply. >>>>>> I assume I can safely ignore the "Upgrade cluster compatibility" >>>>>> warning until libvirt 6.6 gets pushed to CentOS 8.3? >>>>>> >>>>> >>>>> We are working on releasing AV 8.3, hopefully it will be available >>>>> soon, but until that happen you have no way how to upgrade to CL 4.5 and >>>>> you just need to stay in 4.4 >>>>> >>>> >>>> Understood. >>>> >>>> Thanks again. >>>> - Gilboa >>>> >>>> >>> >>> Just updating that oVirt 4.4.4 released yesterday comes with Advanced >>> Virtualization 8.3 so you can now enable CL 4.5. >>> >> >> Sadly enough, even post-full-upgrade (engine + hosts) something seems to >> be broken. >> >> In the WebUI, I see all 3 hosts marked as "up". >> But when I run hosted-engine --vm-status (or migrate the hosted engine), >> only the first (original deployed) host is available. >> I tried "reinstalling" (from the WebUI) the two hosts, no errors, no >> change. >> I tried upgrading the cluster again, host 2 / 3 (the "missing" hosts) >> upgrade is successful; hosts1 fails (cannot migrate the hosted engine). >> >> Any idea what's broken? >> >> - Gilboa >> >> > I'll remove the problematic hosts, re-add them, and reconfigure the > network(s). Let's see if it works. > > - Gilboa > > Sorry for the noise. No go. Cleaned up the hosts via ovirt-hosted-engine-cleanup + reboot, tried "adding" them again, to no avail. Host marked as "up" in WebUI, network correctly configured, however, hosted-engine.conf isn't being created (see log below), ovirt-ha-broker/agent services cannot start and vm-status only shows one host. - Gilboa _______________________________________________ Users mailing list -- users(a)ovirt.org To unsubscribe send an email to users-leave(a)ovirt.org Privacy Statement: https://www.ovirt.org/privacy-policy.html oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/2JEBBBCTAB5...

On Wed, Dec 23, 2020 at 6:28 PM Gilboa Davara <gilboad(a)gmail.com&gt; wrote: > On Wed, Dec 23, 2020 at 6:20 PM Gilboa Davara <gilboad(a)gmail.com&gt; > wrote: > > On Tue, Dec 22, 2020 at 11:45 AM Sandro Bonazzola < > > sbonazzo(a)redhat.com&gt; wrote: > > > Il giorno mer 16 dic 2020 alle ore 17:43 Gilboa Davara < > > > gilboad(a)gmail.com&gt; ha scritto: > > > > On Wed, Dec 16, 2020 at 6:21 PM Martin Perina < > > > > mperina(a)redhat.com&gt; wrote: > > > > > > > > > > On Wed, Dec 16, 2020 at 4:59 PM Gilboa Davara < > > > > > gilboad(a)gmail.com&gt; wrote: > > > > > > Thanks for the prompt reply. > > > > > > I assume I can safely ignore the "Upgrade cluster > > > > > > compatibility" warning until libvirt 6.6 gets pushed to > > > > > > CentOS 8.3? > > > > > > > > > > We are working on releasing AV 8.3, hopefully it will be > > > > > available soon, but until that happen you have no way how > > > > > to upgrade to CL 4.5 and you just need to stay in 4.4 > > > > > > > > Understood. > > > > > > > > Thanks again. > > > > - Gilboa > > > > > > > > > > Just updating that oVirt 4.4.4 released yesterday comes with > > > Advanced Virtualization 8.3 so you can now enable CL 4.5. > > > > Sadly enough, even post-full-upgrade (engine + hosts) something > > seems to be broken. > > > > In the WebUI, I see all 3 hosts marked as "up". > > But when I run hosted-engine --vm-status (or migrate the hosted > > engine), only the first (original deployed) host is available. > > I tried "reinstalling" (from the WebUI) the two hosts, no errors, > > no change. > > I tried upgrading the cluster again, host 2 / 3 (the "missing" > > hosts) upgrade is successful; hosts1 fails (cannot migrate the > > hosted engine). > > > > Any idea what's broken? > > > > - Gilboa > > > > > > I'll remove the problematic hosts, re-add them, and reconfigure the > network(s). Let's see if it works. > > - Gilboa > Sorry for the noise. No go. Cleaned up the hosts via ovirt-hosted-engine-cleanup + reboot, tried "adding" them again, to no avail. Host marked as "up" in WebUI, network correctly configured, however, hosted-engine.conf isn't being created (see log below), ovirt-ha- broker/agent services cannot start and vm-status only shows one host. - Gilboa _______________________________________________Users mailing list -- users(a)ovirt.org To unsubscribe send an email to users-leave(a)ovirt.org Privacy Statement: https://www.ovirt.org/privacy-policy.html oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/2JEBBBCTAB5...

Hello all, Found the problem (at least I think so), but not the solution. As I have an existing Gluster setup (quite complex one) this was the first time I didn't use the "Hyperconverged gluster wizard" (via cockpit), but used the "hosted-engine --deploy" cli instead (which I usually use to deploy single host setups). The idea being: Deploy the first hosts (via cli) and then add the two additional hosts via compute->host->create. For some odd reason I seem to remember this method was an approved way of deploying an hyperconverged gluster setup, in cases you don't want to let a wizard create the gluster bricks. Am I wrong? A. In case I'm wrong: How can I deploy a 3 host hyperconverged setup, _while_ using the preexisting gluster bricks (data/export/iso)? B. I did a clean redeploy (via cockpit -> hosted engine -> hosted engine deploy) and the cluster version is still 4.4 (and given the fact it only deploys a single host, there's no way to upgrade it to 4.5, as I cannot put the host into maintenance and I cannot add additional hosts). - Gilboa On Thu, Dec 24, 2020 at 12:50 PM Strahil Nikolov <hunter86_bg(a)yahoo.com&gt; wrote: > Are you sure you have installed them with HE support ? > > Best Regards, > Strahil Nikolov > В 19:06 +0200 на 23.12.2020 (ср), Gilboa Davara написа: > > > On Wed, Dec 23, 2020 at 6:28 PM Gilboa Davara <gilboad(a)gmail.com&gt; wrote: > > > > On Wed, Dec 23, 2020 at 6:20 PM Gilboa Davara <gilboad(a)gmail.com&gt; wrote: > > On Tue, Dec 22, 2020 at 11:45 AM Sandro Bonazzola <sbonazzo(a)redhat.com&gt; > wrote: > > > > Il giorno mer 16 dic 2020 alle ore 17:43 Gilboa Davara <gilboad(a)gmail.com&gt; > ha scritto: > > On Wed, Dec 16, 2020 at 6:21 PM Martin Perina <mperina(a)redhat.com&gt; wrote: > > > > On Wed, Dec 16, 2020 at 4:59 PM Gilboa Davara <gilboad(a)gmail.com&gt; wrote: > > Thanks for the prompt reply. > I assume I can safely ignore the "Upgrade cluster compatibility" warning > until libvirt 6.6 gets pushed to CentOS 8.3? > > > We are working on releasing AV 8.3, hopefully it will be available soon, > but until that happen you have no way how to upgrade to CL 4.5 and you just > need to stay in 4.4 > > > Understood. > > Thanks again. > - Gilboa > > > > Just updating that oVirt 4.4.4 released yesterday comes with Advanced > Virtualization 8.3 so you can now enable CL 4.5. > > > Sadly enough, even post-full-upgrade (engine + hosts) something seems to > be broken. > > In the WebUI, I see all 3 hosts marked as "up". > But when I run hosted-engine --vm-status (or migrate the hosted engine), > only the first (original deployed) host is available. > I tried "reinstalling" (from the WebUI) the two hosts, no errors, no > change. > I tried upgrading the cluster again, host 2 / 3 (the "missing" hosts) > upgrade is successful; hosts1 fails (cannot migrate the hosted engine). > > Any idea what's broken? > > - Gilboa > > > > I'll remove the problematic hosts, re-add them, and reconfigure the > network(s). Let's see if it works. > > - Gilboa > > > > Sorry for the noise. No go. > Cleaned up the hosts via ovirt-hosted-engine-cleanup + reboot, tried > "adding" them again, to no avail. > Host marked as "up" in WebUI, network correctly configured, however, > hosted-engine.conf isn't being created (see log below), > ovirt-ha-broker/agent services cannot start and vm-status only shows one > host. > > - Gilboa > > _______________________________________________ > > Users mailing list -- > > users(a)ovirt.org > > > To unsubscribe send an email to > > users-leave(a)ovirt.org > > > Privacy Statement: > > https://www.ovirt.org/privacy-policy.html > > > oVirt Code of Conduct: > > https://www.ovirt.org/community/about/community-guidelines/ > > > List Archives: > > https://lists.ovirt.org/archives/list/users@ovirt.org/message/2JEBBBCTAB5... > > >

In the WebUI, I see all 3 hosts marked as "up". But when I run hosted-engine --vm-status (or migrate the hosted engine), only the first (original deployed) host is available. I tried "reinstalling" (from the WebUI) the two hosts, no errors, no change. I tried upgrading the cluster again, host 2 / 3 (the "missing" hosts) upgrade is successful; hosts1 fails (cannot migrate the hosted engine). Start debugging from the hosts that are not seen via "hosted-engine --vm-status". There are 2 log files to check: /var/log/ovirt-hosted-engine-ha/{broker,agent}.log Just check what they are complaining about. Also , you need both ovirt-ha-broker.service and ovirt-ha-agent.service up and running. If there is an issue, the ovirt-ha-agent is being restarted (so it's expected behaviour). Usually the broker should stop complaining and then the agent will kick in. Best Regards, Strahil Nikolov

I "forked" this email into a new subject ("Manually deploying a hyperconverged setup with an existing gluster bricks")But nevertheless, no idea if its intended or not, but it seems that adding a host via "host->computer->create" doesn't create the necessary /etc/ovirt-hosted-engine/hosted-engine.conf configuration on the new hosts, preventing ovirt-ha-* services from starting.

Hello, Reinstall w/ redeploy produced the same results. - Gilboa On Thu, Dec 24, 2020 at 8:07 PM Strahil Nikolov < hunter86_bg(a)yahoo.com&gt; wrote: > > I "forked" this email into a new subject ("Manually deploying a > > hyperconverged setup with an existing gluster bricks")But > > nevertheless, no idea if its intended or not, but it seems that > > adding a host via "host->computer->create" doesn't create the > > necessary /etc/ovirt-hosted-engine/hosted-engine.conf > > configuration on the new hosts, preventing ovirt-ha-* services > > from starting. > > > > So , set the host into maintenance and > then select installation -> reinstall -> Hosted Engine -> Deploy > > Best Regards, > Strahil Nikolov _______________________________________________Users mailing list -- users(a)ovirt.org To unsubscribe send an email to users-leave(a)ovirt.org Privacy Statement: https://www.ovirt.org/privacy-policy.html oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/KHBX2LRHIPH...

On Fri, Dec 25, 2020 at 7:41 PM Strahil Nikolov <hunter86_bg(a)yahoo.com&gt; wrote: > Any hints in vdsm logs on the affected host or on the > broker.log/agent.log ? > > Happy Hollidays to everyone! > > Best Regards, > Strahil Nikolov > > Hello, Sorry for the late reply. One of the nodes suffered a major failure and I'm waiting for the tech support to ship replacement parts. Once it's up and running, I'll send the logs. Happy holidays! - Gilboa > В 14:33 +0200 на 25.12.2020 (пт), Gilboa Davara написа: > > Hello, > > Reinstall w/ redeploy produced the same results. > > - Gilboa > > On Thu, Dec 24, 2020 at 8:07 PM Strahil Nikolov <hunter86_bg(a)yahoo.com&gt; > wrote: > > > I "forked" this email into a new subject ("Manually deploying a > hyperconverged setup with an existing gluster bricks") > But nevertheless, no idea if its intended or not, but it seems that > adding a host via "host->computer->create" doesn't create the necessary > /etc/ovirt-hosted-engine/hosted-engine.conf configuration on the new hosts, > preventing ovirt-ha-* services from starting. > > > So , set the host into maintenance and > then select installation -> reinstall -> Hosted Engine -> Deploy > > Best Regards, > Strahil Nikolov > > _______________________________________________ > > Users mailing list -- > > users(a)ovirt.org > > > To unsubscribe send an email to > > users-leave(a)ovirt.org > > > Privacy Statement: > > https://www.ovirt.org/privacy-policy.html > > > oVirt Code of Conduct: > > https://www.ovirt.org/community/about/community-guidelines/ > > > List Archives: > > https://lists.ovirt.org/archives/list/users@ovirt.org/message/KHBX2LRHIPH... > > >