Bug 1819514

Summary: Failed to register 4.4 host to the latest engine (4.4.0-0.29.master.el8ev)
Product: Red Hat Enterprise Virtualization Manager Reporter: cshao <cshao>
Component: ovirt-engineAssignee: Dana <delfassy>
Status: CLOSED ERRATA QA Contact: cshao <cshao>
Severity: urgent Docs Contact:
Priority: high    
Version: 4.4.0CC: cshao, dfodor, lsvaty, mavital, michal.skrivanek, mperina, mtessun, nlevy, peyu, qiyuan, sbonazzo, shlei, weiwang, yaniwang, yturgema
Target Milestone: ovirt-4.4.0Keywords: Regression, Reopened
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: rhvm-4.4.0-0.31 ovirt-engine-4.4.0_beta3 rhv-4.4.0-30 Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-08-04 13:22:22 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:
Attachments:
Description Flags
host + engine all logs none

Description cshao 2020-04-01 02:12:03 UTC
Created attachment 1675279 [details]
host + engine all logs

Description of problem:
Failed to register 4.4 host to the latest engine (4.4.0-0.29.master.el8ev)

Host cshao installation failed. Task Reset configuration of advanced virtualization module failed to execute: .

Version-Release number of selected component (if applicable):
Host:
redhat-virtualization-host-4.4.0-20200330.0.el8_2
vdsm-4.40.9-1.el8ev.x86_64

Engine:
ovirt-engine-4.4.0-0.29.master.el8ev.noarch


How reproducible:
100%

Steps to Reproduce:
1. Install RHVH-4.4-20200330.0-RHVH-x86_64-dvd1.iso via anaconda GUI.
2. Register to the latest engine.
3.

Actual results:
Failed to register 4.4 host to the latest engine (4.4.0-0.29.master.el8ev)

Expected results:
Register to engine can succeed.

Additional info:
No such issue on previous engine(4.4.0-0.26.master.el8e), so it is a engine regression bug

Comment 9 Michal Skrivanek 2020-04-01 13:51:17 UTC
already reported in bug 1819248

*** This bug has been marked as a duplicate of bug 1819248 ***

Comment 10 Martin Perina 2020-04-02 12:41:50 UTC
Reopening, this is not a duplicate of BZ1819248.

We have this error during host deploy:

{"changed": true,
 "cmd": "dnf -y module reset virt",
 "delta": "0:00:05.459894", 
 "end": "2020-04-01 01:42:06.620621",
 "msg": "non-zero return code",
 "rc": 1, 
 "start": "2020-04-01 01:42:01.160727",
 "stderr": "Unable to resolve argument virt\nError: Problems in request:\nmissing groups or modules: virt",
 "stderr_lines": ["Unable to resolve argument virt", "Error: Problems in request:", "missing groups or modules: virt"],
 "stdout": "Updating Subscription Management repositories.\nUnable to read consumer identity\nThis system is not registered to Red Hat Subscription Management. You can use subscription-manager to register.",
 "stdout_lines": ["Updating Subscription Management repositories.", "Unable to read consumer identity", "This system is not registered to Red Hat Subscription Management. You can use subscription-manager to register."]}

It looks like there is an error reseting advanced virt module on RHVH.

So how we should handle RHVH? To enable advanced virt module or not? If not, how can we detect that a host is a NGN or RHVH and not CentOS/RHEL?

Comment 11 Yuval Turgeman 2020-04-02 12:46:08 UTC
IIUC we will not be shipping the virt module in the rhvh channel.  What we do, is ship the content of the virt module inside the image so I think we can skip this step in rhvh

Comment 12 Yuval Turgeman 2020-04-02 12:53:33 UTC
As for detecting you can check in /etc/os-release if VARIANT_ID is ovirt-node.  Another alternative is to try and execute `imgbase w`, if it works, then it's probably ovirt-node-ng/rhvh

Comment 13 Yuval Turgeman 2020-04-02 13:33:20 UTC
Another way is to detect if we're on ngn/rhvh is to check if either file exists: /usr/lib/os.release.d/ovirt-release-host-node or /usr/lib/os.release.d/os-release-rhv-host

Comment 16 cshao 2020-04-10 04:38:26 UTC
Test version:
engine: 4.4.0-0.32.master.el8ev
redhat-virtualization-host-4.4.0-20200409.1.el8_2

Register RHVH to engine can succeed, so the bug is fixed. Change bug status to VERIFIED.

Comment 18 errata-xmlrpc 2020-08-04 13:22:22 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Important: RHV Manager (ovirt-engine) 4.4 security, bug fix, and enhancement update), and where to find the updated
files, follow the link below.

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

https://access.redhat.com/errata/RHSA-2020:3247