Cannot upgrade cluster to v4.5 (All hosts are CentOS 8.3.2011)
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
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@gmail.com> 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@ovirt.org To unsubscribe send an email to users-leave@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/7CCUHPEGVZD3BB...
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@redhat.com> 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@gmail.com> 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@ovirt.org To unsubscribe send an email to users-leave@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/7CCUHPEGVZD3BB...
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@redhat.com> 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@gmail.com> 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
On Wed, Dec 16, 2020 at 2:25 PM Gilboa Davara <gilboad@gmail.com> wrote: particular libvirt 6.6)
Thanks, - Gilboa _______________________________________________ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-leave@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/7CCUHPEGVZD3BB...
_______________________________________________ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-leave@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/RMZ3S64FFIOFTR...
-- Martin Perina Manager, Software Engineering Red Hat Czech s.r.o.
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@redhat.com> wrote:
On Wed, Dec 16, 2020 at 2:25 PM Gilboa Davara <gilboad@gmail.com> 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@redhat.com> 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@gmail.com> 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@ovirt.org To unsubscribe send an email to users-leave@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/7CCUHPEGVZD3BB...
_______________________________________________ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-leave@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/RMZ3S64FFIOFTR...
-- Martin Perina Manager, Software Engineering Red Hat Czech s.r.o.
On Wed, Dec 16, 2020 at 4:59 PM Gilboa Davara <gilboad@gmail.com> 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
- Gilboa
On Wed, Dec 16, 2020 at 5:56 PM Martin Perina <mperina@redhat.com> wrote:
On Wed, Dec 16, 2020 at 2:25 PM Gilboa Davara <gilboad@gmail.com> 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@redhat.com> 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@gmail.com> 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@ovirt.org To unsubscribe send an email to users-leave@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/7CCUHPEGVZD3BB...
_______________________________________________ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-leave@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/RMZ3S64FFIOFTR...
-- Martin Perina Manager, Software Engineering Red Hat Czech s.r.o.
-- Martin Perina Manager, Software Engineering Red Hat Czech s.r.o.
On Wed, Dec 16, 2020 at 6:21 PM Martin Perina <mperina@redhat.com> wrote:
On Wed, Dec 16, 2020 at 4:59 PM Gilboa Davara <gilboad@gmail.com> 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@redhat.com> wrote:
On Wed, Dec 16, 2020 at 2:25 PM Gilboa Davara <gilboad@gmail.com> 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@redhat.com> 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@gmail.com> 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@ovirt.org To unsubscribe send an email to users-leave@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/7CCUHPEGVZD3BB...
_______________________________________________ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-leave@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/RMZ3S64FFIOFTR...
-- Martin Perina Manager, Software Engineering Red Hat Czech s.r.o.
-- Martin Perina Manager, Software Engineering Red Hat Czech s.r.o.
Il giorno mer 16 dic 2020 alle ore 17:43 Gilboa Davara <gilboad@gmail.com> ha scritto:
On Wed, Dec 16, 2020 at 6:21 PM Martin Perina <mperina@redhat.com> wrote:
On Wed, Dec 16, 2020 at 4:59 PM Gilboa Davara <gilboad@gmail.com> 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.
- Gilboa
On Wed, Dec 16, 2020 at 5:56 PM Martin Perina <mperina@redhat.com> wrote:
On Wed, Dec 16, 2020 at 2:25 PM Gilboa Davara <gilboad@gmail.com> 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@redhat.com> 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@gmail.com> 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@ovirt.org > To unsubscribe send an email to users-leave@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/7CCUHPEGVZD3BB... > _______________________________________________ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-leave@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/RMZ3S64FFIOFTR...
-- 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@ovirt.org To unsubscribe send an email to users-leave@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/OEL5Y7UYBGLOTK...
-- Sandro Bonazzola MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV Red Hat EMEA <https://www.redhat.com/> sbonazzo@redhat.com <https://www.redhat.com/> *Red Hat respects your work life balance. Therefore there is no need to answer this email out of your office hours. <https://mojo.redhat.com/docs/DOC-1199578>*
On Tue, Dec 22, 2020 at 11:45 AM Sandro Bonazzola <sbonazzo@redhat.com> wrote:
Il giorno mer 16 dic 2020 alle ore 17:43 Gilboa Davara <gilboad@gmail.com> ha scritto:
On Wed, Dec 16, 2020 at 6:21 PM Martin Perina <mperina@redhat.com> wrote:
On Wed, Dec 16, 2020 at 4:59 PM Gilboa Davara <gilboad@gmail.com> 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@redhat.com> wrote:
On Wed, Dec 16, 2020 at 2:25 PM Gilboa Davara <gilboad@gmail.com> 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@redhat.com> 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@gmail.com> > 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:20 PM Gilboa Davara <gilboad@gmail.com> wrote:
On Tue, Dec 22, 2020 at 11:45 AM Sandro Bonazzola <sbonazzo@redhat.com> wrote:
Il giorno mer 16 dic 2020 alle ore 17:43 Gilboa Davara <gilboad@gmail.com> ha scritto:
On Wed, Dec 16, 2020 at 6:21 PM Martin Perina <mperina@redhat.com> wrote:
On Wed, Dec 16, 2020 at 4:59 PM Gilboa Davara <gilboad@gmail.com> 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
- Gilboa
On Wed, Dec 16, 2020 at 5:56 PM Martin Perina <mperina@redhat.com> wrote:
On Wed, Dec 16, 2020 at 2:25 PM Gilboa Davara <gilboad@gmail.com> 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@redhat.com> > 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@gmail.com> >> 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@gmail.com> wrote:
On Wed, Dec 23, 2020 at 6:20 PM Gilboa Davara <gilboad@gmail.com> wrote:
On Tue, Dec 22, 2020 at 11:45 AM Sandro Bonazzola <sbonazzo@redhat.com> wrote:
Il giorno mer 16 dic 2020 alle ore 17:43 Gilboa Davara < gilboad@gmail.com> ha scritto:
On Wed, Dec 16, 2020 at 6:21 PM Martin Perina <mperina@redhat.com> wrote:
On Wed, Dec 16, 2020 at 4:59 PM Gilboa Davara <gilboad@gmail.com> 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
Hello, If I understand the problem correctly , you are facing the problem of migrating the HE VM, If Yes, I suspect the issue is all the cores have been allocated to the HE VM and because of this migration to other hosts not showing please verify once with hypervisor available core to HE VM allocated core. On Wed, Dec 23, 2020 at 10:38 PM Gilboa Davara <gilboad@gmail.com> wrote:
On Wed, Dec 23, 2020 at 6:28 PM Gilboa Davara <gilboad@gmail.com> wrote:
On Wed, Dec 23, 2020 at 6:20 PM Gilboa Davara <gilboad@gmail.com> wrote:
On Tue, Dec 22, 2020 at 11:45 AM Sandro Bonazzola <sbonazzo@redhat.com> wrote:
Il giorno mer 16 dic 2020 alle ore 17:43 Gilboa Davara < gilboad@gmail.com> ha scritto:
On Wed, Dec 16, 2020 at 6:21 PM Martin Perina <mperina@redhat.com> wrote:
On Wed, Dec 16, 2020 at 4:59 PM Gilboa Davara <gilboad@gmail.com> 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@ovirt.org To unsubscribe send an email to users-leave@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/2JEBBBCTAB5JV2...
On Wed, Dec 23, 2020 at 7:08 PM Gilboa Davara <gilboad@gmail.com> wrote:
On Wed, Dec 23, 2020 at 6:28 PM Gilboa Davara <gilboad@gmail.com> wrote:
On Wed, Dec 23, 2020 at 6:20 PM Gilboa Davara <gilboad@gmail.com> wrote:
On Tue, Dec 22, 2020 at 11:45 AM Sandro Bonazzola <sbonazzo@redhat.com> wrote:
Il giorno mer 16 dic 2020 alle ore 17:43 Gilboa Davara <gilboad@gmail.com> ha scritto:
On Wed, Dec 16, 2020 at 6:21 PM Martin Perina <mperina@redhat.com> wrote:
On Wed, Dec 16, 2020 at 4:59 PM Gilboa Davara <gilboad@gmail.com> 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.
Not sure which log you intended to attach (and forgot?), but please check/share all relevant logs - it's hard to guess what the problem is: - Everything under /var/log/ovirt-engine, including subdirs, from the engine - syslog/journal (/var/log/messages, 'journalctl'), /var/log/vdsm/, /var/log/ovirt-* from the hosts (including the working host). Also, although I do not think this is your problem, please note that ovirt-hosted-engine-cleanup does not clean up everything. I recently pushed a patch to it to remove a bit more [1] (should be in 4.4.4, I think - you can get it from master-snapshot if you want), but still. If unsure, better reinstall the OS. [1] https://gerrit.ovirt.org/c/ovirt-hosted-engine-setup/+/112336 Thanks and best regards, -- Didi
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@gmail.com> wrote:
On Wed, Dec 23, 2020 at 6:20 PM Gilboa Davara <gilboad@gmail.com> wrote:
On Tue, Dec 22, 2020 at 11:45 AM Sandro Bonazzola < sbonazzo@redhat.com> wrote:
Il giorno mer 16 dic 2020 alle ore 17:43 Gilboa Davara < gilboad@gmail.com> ha scritto:
On Wed, Dec 16, 2020 at 6:21 PM Martin Perina < mperina@redhat.com> wrote:
On Wed, Dec 16, 2020 at 4:59 PM Gilboa Davara < gilboad@gmail.com> 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@ovirt.org To unsubscribe send an email to users-leave@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/2JEBBBCTAB5JV2...
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@yahoo.com> 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@gmail.com> wrote:
On Wed, Dec 23, 2020 at 6:20 PM Gilboa Davara <gilboad@gmail.com> wrote:
On Tue, Dec 22, 2020 at 11:45 AM Sandro Bonazzola <sbonazzo@redhat.com> wrote:
Il giorno mer 16 dic 2020 alle ore 17:43 Gilboa Davara <gilboad@gmail.com> ha scritto:
On Wed, Dec 16, 2020 at 6:21 PM Martin Perina <mperina@redhat.com> wrote:
On Wed, Dec 16, 2020 at 4:59 PM Gilboa Davara <gilboad@gmail.com> 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@ovirt.org
To unsubscribe send an email to
users-leave@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/2JEBBBCTAB5JV2...
P.S. When creating a host, "Choose hosted engine deployment action" was set to "deploy". - Gilboa On Thu, Dec 24, 2020 at 4:53 PM Gilboa Davara <gilboad@gmail.com> wrote:
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@yahoo.com> 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@gmail.com> wrote:
On Wed, Dec 23, 2020 at 6:20 PM Gilboa Davara <gilboad@gmail.com> wrote:
On Tue, Dec 22, 2020 at 11:45 AM Sandro Bonazzola <sbonazzo@redhat.com> wrote:
Il giorno mer 16 dic 2020 alle ore 17:43 Gilboa Davara <gilboad@gmail.com> ha scritto:
On Wed, Dec 16, 2020 at 6:21 PM Martin Perina <mperina@redhat.com> wrote:
On Wed, Dec 16, 2020 at 4:59 PM Gilboa Davara <gilboad@gmail.com> 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@ovirt.org
To unsubscribe send an email to
users-leave@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/2JEBBBCTAB5JV2...
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
Hello, On Thu, Dec 24, 2020 at 12:45 PM Strahil Nikolov <hunter86_bg@yahoo.com> wrote:
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. Thanks, Gilboa
On Thu, Dec 24, 2020 at 5:04 PM Gilboa Davara <gilboad@gmail.com> wrote:
Hello,
On Thu, Dec 24, 2020 at 12:45 PM Strahil Nikolov <hunter86_bg@yahoo.com> wrote:
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.
Thanks, Gilboa
Typo: ...it seems that adding a host via "Compute -> Host > Create" - Gilboa
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
Hello, Reinstall w/ redeploy produced the same results. - Gilboa On Thu, Dec 24, 2020 at 8:07 PM Strahil Nikolov <hunter86_bg@yahoo.com> 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
Any hints in vdsm logs on the affected host or on the broker.log/agent.log ? Happy Hollidays to everyone! Best Regards,Strahil Nikolov В 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@yahoo.com> 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@ovirt.org To unsubscribe send an email to users-leave@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/KHBX2LRHIPHRJF...
On Fri, Dec 25, 2020 at 7:41 PM Strahil Nikolov <hunter86_bg@yahoo.com> 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@yahoo.com> 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@ovirt.org
To unsubscribe send an email to
users-leave@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/KHBX2LRHIPHRJF...
Short update. 1. Ran ovirt-hosted-engine-cleanup on all 3 nodes. 2. Installed hosted engine on the first engine via hosted-engine --deploy (w/ gluster storage). 3. Added the two remaining hosts using host -> new -> w/ hosted engine -> deploy. 4. All machines are up and running and I can see theme in hosted-engine --vm-status and they all have a valid score (3400). 5. But... Tried upgrading the cluster to 4.5, no errors, but cluster is still in 4.4 :/ - Gilboa On Mon, Dec 28, 2020 at 4:29 PM Gilboa Davara <gilboad@gmail.com> wrote:
On Fri, Dec 25, 2020 at 7:41 PM Strahil Nikolov <hunter86_bg@yahoo.com> 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@yahoo.com> 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@ovirt.org
To unsubscribe send an email to
users-leave@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/KHBX2LRHIPHRJF...
Engine log attached. (Looks clean) - Gilboa On Wed, Dec 30, 2020 at 4:30 PM Gilboa Davara <gilboad@gmail.com> wrote:
Short update. 1. Ran ovirt-hosted-engine-cleanup on all 3 nodes. 2. Installed hosted engine on the first engine via hosted-engine --deploy (w/ gluster storage). 3. Added the two remaining hosts using host -> new -> w/ hosted engine -> deploy. 4. All machines are up and running and I can see theme in hosted-engine --vm-status and they all have a valid score (3400). 5. But... Tried upgrading the cluster to 4.5, no errors, but cluster is still in 4.4 :/
- Gilboa
On Mon, Dec 28, 2020 at 4:29 PM Gilboa Davara <gilboad@gmail.com> wrote:
On Fri, Dec 25, 2020 at 7:41 PM Strahil Nikolov <hunter86_bg@yahoo.com> 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@yahoo.com> 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@ovirt.org
To unsubscribe send an email to
users-leave@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/KHBX2LRHIPHRJF...
Maybe there is a missing package that is preventing that. Let's see what the devs will find out next year (thankfully you wpn't have to wait much). Best Regards, Strahil Nikolov В сряда, 30 декември 2020 г., 16:30:37 Гринуич+2, Gilboa Davara <gilboad@gmail.com> написа: Short update. 1. Ran ovirt-hosted-engine-cleanup on all 3 nodes. 2. Installed hosted engine on the first engine via hosted-engine --deploy (w/ gluster storage). 3. Added the two remaining hosts using host -> new -> w/ hosted engine -> deploy. 4. All machines are up and running and I can see theme in hosted-engine --vm-status and they all have a valid score (3400). 5. But... Tried upgrading the cluster to 4.5, no errors, but cluster is still in 4.4 :/ - Gilboa On Mon, Dec 28, 2020 at 4:29 PM Gilboa Davara <gilboad@gmail.com> wrote:
On Fri, Dec 25, 2020 at 7:41 PM Strahil Nikolov <hunter86_bg@yahoo.com> 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@yahoo.com> 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@ovirt.orgTo unsubscribe send an email to users-leave@ovirt.orgPrivacy Statement: https://www.ovirt.org/privacy-policy.htmloVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/KHBX2LRHIPHRJF...
Many thanks. Happy new year. - Gilboa On Wed, Dec 30, 2020 at 9:12 PM Strahil Nikolov <hunter86_bg@yahoo.com> wrote:
Maybe there is a missing package that is preventing that. Let's see what the devs will find out next year (thankfully you wpn't have to wait much).
Best Regards, Strahil Nikolov
В сряда, 30 декември 2020 г., 16:30:37 Гринуич+2, Gilboa Davara < gilboad@gmail.com> написа:
Short update. 1. Ran ovirt-hosted-engine-cleanup on all 3 nodes. 2. Installed hosted engine on the first engine via hosted-engine --deploy (w/ gluster storage). 3. Added the two remaining hosts using host -> new -> w/ hosted engine -> deploy. 4. All machines are up and running and I can see theme in hosted-engine --vm-status and they all have a valid score (3400). 5. But... Tried upgrading the cluster to 4.5, no errors, but cluster is still in 4.4 :/
- Gilboa
On Mon, Dec 28, 2020 at 4:29 PM Gilboa Davara <gilboad@gmail.com> wrote:
On Fri, Dec 25, 2020 at 7:41 PM Strahil Nikolov <hunter86_bg@yahoo.com>
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@yahoo.com>
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,
wrote: 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@ovirt.orgTo unsubscribe send an email to users-leave@ovirt.orgPrivacy Statement: https://www.ovirt.org/privacy-policy.htmloVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/KHBX2LRHIPHRJF...
participants (7)
-
Gilboa Davara -
Martin Perina -
Ritesh Chikatwar -
Sandro Bonazzola -
Shani Leviim -
Strahil Nikolov -
Yedidyah Bar David