Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1878467

Summary:	Can't join rhel8.3 host into new cluster 4.5
Product:	[oVirt] vdsm	Reporter:	Michael Burman <mburman>
Component:	General	Assignee:	Eli Mesika <emesika>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Petr Matyáš <pmatyas>
Severity:	high	Docs Contact:
Priority:	high
Version:	4.40.29	CC:	bugs, michal.skrivanek, mperina, nsoffer
Target Milestone:	ovirt-4.4.3	Keywords:	AutomationBlocker
Target Release:	---	Flags:	mperina: ovirt-4.4?
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:	vdsm-4.40.30	Doc Type:	No Doc Update
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-11-11 06:42:37 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	Infra	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	1877675
Bug Blocks:

Description Michael Burman 2020-09-13 08:44:02 UTC

Description of problem:
Can't join rhel8.3 host into new cluster 4.5

rhvm-4.4.3.2-0.19.el8ev.noarch introduced new cluster level 4.5 for rhel8.3 hosts.
We can't add or activate rhel8.3 hosts in this new cluster:
"Host 'host_name' is compatible with versions (4.2,4.3,4.4) and cannot join Cluster Cluster1 which is set to version 4.5."

The issue relevant for the HE flow and blocking our automation.

Version-Release number of selected component (if applicable):
rhvm-4.4.3.2-0.19.el8ev.noarch

How reproducible:
100%

Steps to Reproduce:
1. Install or update to rhvm-4.4.3.2-0.19.el8ev.noarch
2. Update cluster level to 4.5 or create new
3. Try to activate or add rhel8.3 into this new cluster

Actual results:
Failed

Expected results:
Must work

Additional info:
Looks like vdsm missing version 4.5

Comment 1 Michael Burman 2020-09-13 08:46:09 UTC

vdsm-client Host getCapabilities|less


 "clusterLevels": [
        "4.2",
        "4.3",
        "4.4"
    ],

Comment 3 Nir Soffer 2020-09-13 16:25:36 UTC

Please share libvirt version on the 8.3 host:

    rpm -q libvrit-daemon

This is what I have on my test setup:

# rpm -q libvirt-daemon
libvirt-daemon-6.6.0-4.module+el8.3.0+7883+3d717aa8.x86_64

# vdsm-client Host getCapabilities | jq .clusterLevels
[
  "4.2",
  "4.3",
  "4.4",
  "4.5"
]

Comment 4 Michael Burman 2020-09-14 05:27:28 UTC

(In reply to Nir Soffer from comment #3)
> Please share libvirt version on the 8.3 host:
> 
>     rpm -q libvrit-daemon
> 
> This is what I have on my test setup:
> 
> # rpm -q libvirt-daemon
> libvirt-daemon-6.6.0-4.module+el8.3.0+7883+3d717aa8.x86_64
> 
> # vdsm-client Host getCapabilities | jq .clusterLevels
> [
>   "4.2",
>   "4.3",
>   "4.4",
>   "4.5"
> ]

HI NIr,

It's not related to libvirt.  vdsm-4.40.29-1.el8ev.x86_64 is missing cluster level 4.5 capabilities.
I have same libvirt-daemon-6.6.0-4.module+el8.3.0+7883+3d717aa8.x86_64

Comment 5 Martin Perina 2020-09-14 06:18:21 UTC

Cluster 4.5 on VDSM will be supported only onl vdsm 4.40.30, which will be in qe compose this week. Until then don't use cluster level 4.5

Comment 7 Petr Matyáš 2020-09-21 13:02:40 UTC

Verified on vdsm-4.40.30-1.el8ev.x86_64

Comment 8 Sandro Bonazzola 2020-11-11 06:42:37 UTC

This bugzilla is included in oVirt 4.4.3 release, published on November 10th 2020.

Since the problem described in this bug report should be resolved in oVirt 4.4.3 release, it has been closed with a resolution of CURRENT RELEASE.

If the solution does not work for you, please open a new bug report.