On Tue, Dec 22, 2020 at 11:45 AM Sandro Bonazzola <sbonazzo(a)redhat.com>
wrote:
Il giorno mer 16 dic 2020 alle ore 17:43 Gilboa Davara <gilboad(a)gmail.com>
ha scritto:
> On Wed, Dec 16, 2020 at 6:21 PM Martin Perina <mperina(a)redhat.com> wrote:
>
>>
>>
>> On Wed, Dec 16, 2020 at 4:59 PM Gilboa Davara <gilboad(a)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(a)redhat.com>
>>> wrote:
>>>
>>>>
>>>>
>>>> On Wed, Dec 16, 2020 at 2:25 PM Gilboa Davara <gilboad(a)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(a)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(a)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
>>>>>>> _______________________________________________
>>>>>>
>>>>>>