Bug 1718399 - Add yum-utils to ovirt-engine-appliance to unlock disconnected deployments
Summary: Add yum-utils to ovirt-engine-appliance to unlock disconnected deployments
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: ovirt-appliance
Classification: oVirt
Component: Packaging.rpm
Version: 4.3.4
Hardware: Unspecified
OS: Unspecified
medium
high
Target Milestone: ovirt-4.3.5
: 4.3.5
Assignee: Yuval Turgeman
QA Contact: Nikolai Sednev
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-06-07 16:17 UTC by Simone Tiraboschi
Modified: 2019-07-30 14:08 UTC (History)
4 users (show)

Fixed In Version: rhvm-appliance-4.3-20190703.2.el7, ovirt-engine-appliance-4.3-20190703.1.el7
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-07-30 14:08:42 UTC
oVirt Team: Node
Embargoed:
mtessun: ovirt-4.3+
mtessun: planning_ack+
sbonazzo: devel_ack+
mavital: testing_ack+


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 100861 0 'None' MERGED build: add yum-utils to appliance 2020-02-23 07:41:46 UTC
oVirt gerrit 100863 0 'None' MERGED build: add yum-utils to appliance 2020-02-23 07:41:46 UTC

Description Simone Tiraboschi 2019-06-07 16:17:19 UTC
Description of problem:
ansible-yum module, used in ovirt-ansible-engine-setup, is always try to implicitly install yum-utils for its internal purposes:
See:
https://github.com/ansible/ansible/blame/devel/lib/ansible/modules/packaging/os/yum.py#L1545

ovirt-engine-appliance doesn't include yum-utils and so the deployment always fails on disconnected env even if everything else is always there.


Version-Release number of selected component (if applicable):
4.3.4

How reproducible:
100%

Steps to Reproduce:
1. try to deploy hosted-engine on a disconnected env
2.
3.

Actual results:
hosted-engine setup fails with ansible-yum trying to install yum-utils

Expected results:
yum-utils is already there and we can deploy hosted-engine in a disconnected enviroment

Additional info:

Comment 1 Yuval Turgeman 2019-06-10 07:48:11 UTC
Wow, why do they do this ? Isn't this a packaging bug for ansible ?

Comment 2 Simone Tiraboschi 2019-06-10 07:52:33 UTC
Not really sure: ansible and all its dependencies are installed on the controller host.
yum-utils is going to be installed at runtime on the managed hosts.

Comment 3 Sandro Bonazzola 2019-06-10 10:56:19 UTC
Is the package module doing the same? Or do we need yum module for other reasons?

Comment 4 Simone Tiraboschi 2019-06-10 13:55:42 UTC
No, package module will not.

Yum it's used here in ovirt-ansible-engine-setup:
https://github.com/oVirt/ovirt-ansible-engine-setup/blob/master/tasks/install_packages.yml#L8

with 'list' command to discriminate between oVirt and RHV.

Comment 5 Lukas Svaty 2019-06-17 10:44:32 UTC
We need a clearer specification of 'disconnected env' for QE Ack. 
Or reproduction steps.

Comment 6 Simone Tiraboschi 2019-06-25 15:13:58 UTC
(In reply to Lukas Svaty from comment #5)
> We need a clearer specification of 'disconnected env' for QE Ack. 
> Or reproduction steps.

Try to deploy hosted-engine on an environment with no Internet connection and no proxy for yum:
1. install ovirt-hosted-engine-setup and ovirt-engine-appliance on the host
2. disconnect it from the Internet
3. deploy hosted-engine

Comment 7 Nikolai Sednev 2019-07-15 14:26:02 UTC
Works for me on these components:
ovirt-engine-setup-4.3.5.4-0.1.el7.noarch
ovirt-hosted-engine-ha-2.3.3-1.el7ev.noarch
ovirt-hosted-engine-setup-2.3.11-1.el7ev.noarch
Linux 3.10.0-1060.el7.x86_64 #1 SMP Mon Jul 1 18:28:13 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
Red Hat Enterprise Linux Server release 7.7 Beta (Maipo)

Comment 8 Sandro Bonazzola 2019-07-30 14:08:42 UTC
This bugzilla is included in oVirt 4.3.5 release, published on July 30th 2019.

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


Note You need to log in before you can comment on or make changes to this bug.