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 <slev...@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 <gilb...@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-le...@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/7CCUHPEGVZD3BBLBDTOCHG5J6EEG5DE2/
>>
>
_______________________________________________
Users mailing list -- users@ovirt.org
To unsubscribe send an email to users-le...@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/RMZ3S64FFIOFTRBQOWVTTLCRJJA65EMJ/

Reply via email to