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

Bug 1785272

Summary: Host register failed with yum-utils
Product: [oVirt] ovirt-engine Reporter: Ulhas Surse <usurse>
Component: ovirt-host-deploy-ansibleAssignee: Martin Perina <mperina>
Status: CLOSED CURRENTRELEASE QA Contact: Yaning Wang <yaniwang>
Severity: high Docs Contact:
Priority: unspecified    
Version: 4.4.0CC: bugs, didi, mperina
Target Milestone: ovirt-4.4.0Keywords: Regression
Target Release: ---Flags: pm-rhel: ovirt-4.4+
sbonazzo: blocker?
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-05-20 19:59:36 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:    
Bug Blocks: 1770094, 1779527    

Description Ulhas Surse 2019-12-19 14:49:18 UTC
Description of problem:
While adding ovirt node to ovirt manager, it failed to install with error:

~~~
Host Hypervisor2 installation failed. Task Install yum-utils failed to execute: .
~~~

Version-Release number of selected component (if applicable):
Ovirt Node: ovirt-node-ng-installer-4.4.0-2019121307.el8.iso
            4.4.0-0.1.alpha.20191211173111.git6cf41f5.el8

Ovirt Manager: CentOS-7-x86_64-Minimal-1908.iso
               Software Version:4.4.0-0.0.master.20191211094236.gitfe6ccc6.el7
       
How reproducible:
Always

Steps to Reproduce:
1. Install ovirt node with above version.
2. Try to register it to the ovirt manager
3. it failed

Actual results:
Node is not able to register. 

Expected results:
Node should register successfully. 

Additional info:
Enabling Base repo works to register. 

Deploy logs:
-----------


2019-12-19 20:16:54 IST - TASK [ovirt-host-deploy-facts : Install yum-utils] *****************************
2019-12-19 20:17:27 IST - fatal: [vm205.gsslab.pnq.redhat.com]: FAILED! => {"changed": false, "failures": ["No package yum-utils available."], "msg": "Failed to install some of the specified packages", "rc": 1, "results": []}
2019-12-19 20:17:27 IST - {
  "status" : "OK",
  "msg" : "",
  "data" : {
    "event" : "runner_on_failed",
    "uuid" : "9793bb18-562b-407e-9149-782b3e7f2d65",
    "stdout" : "fatal: [vm205.gsslab.pnq.redhat.com]: FAILED! => {\"changed\": false, \"failures\": [\"No package yum-utils available.\"], \"msg\": \"Failed to install some of the specified packages\", \"rc\": 1, \"results\": []}",

Comment 1 Sandro Bonazzola 2019-12-19 15:21:39 UTC
Martin if yum utils is now required for the deployment we need to add it to ovirt-host as dependency to get it installed and available in oVirt Node.

Note that 4.2 and 4.3 nodes will miss it unless we respin them for including this new dependency or 4.4 engine won't be able to deploy them.

Comment 2 Martin Perina 2019-12-21 18:12:51 UTC
(In reply to Sandro Bonazzola from comment #1)
> Martin if yum utils is now required for the deployment we need to add it to
> ovirt-host as dependency to get it installed and available in oVirt Node.
> 
> Note that 4.2 and 4.3 nodes will miss it unless we respin them for including
> this new dependency or 4.4 engine won't be able to deploy them.

It seems that we no longer need to use repoquery within host deploy flow, so we can remove the dependency.

Comment 3 RHV bug bot 2020-01-08 14:46:49 UTC
INFO: Bug status wasn't changed from MODIFIED to ON_QA due to the following reason:

[Tag 'ovirt-engine-4.4.0' doesn't contain patch 'https://gerrit.ovirt.org/105891']
gitweb: https://gerrit.ovirt.org/gitweb?p=ovirt-engine.git;a=shortlog;h=refs/tags/ovirt-engine-4.4.0

For more info please contact: infra

Comment 4 RHV bug bot 2020-01-08 15:14:57 UTC
INFO: Bug status wasn't changed from MODIFIED to ON_QA due to the following reason:

[Tag 'ovirt-engine-4.4.0' doesn't contain patch 'https://gerrit.ovirt.org/105891']
gitweb: https://gerrit.ovirt.org/gitweb?p=ovirt-engine.git;a=shortlog;h=refs/tags/ovirt-engine-4.4.0

For more info please contact: infra

Comment 5 Yaning Wang 2020-02-03 09:23:05 UTC
Version-Release number of selected component (if applicable):

Ovirt Node: ovirt-node-ng-installer-4.4.0-2020012312.el8.iso
Ovirt Manager: ovirt-engine-4.4.0-0.6.master.noarch


Actual results:

Node register successfully.

Comment 6 Sandro Bonazzola 2020-05-20 19:59:36 UTC
This bugzilla is included in oVirt 4.4.0 release, published on May 20th 2020.

Since the problem described in this bug report should be
resolved in oVirt 4.4.0 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.