Bug 1888628

Summary: Require ansible-2.9.14 in ovirt-hosted-engine-setup
Product: Red Hat Enterprise Virtualization Manager Reporter: Martin Perina <mperina>
Component: ovirt-hosted-engine-setupAssignee: Asaf Rachmani <arachman>
Status: CLOSED ERRATA QA Contact: Nikolai Sednev <nsednev>
Severity: high Docs Contact:
Priority: high    
Version: 4.4.0CC: arachman, delfassy, emarcus, lsurette, mavital, sbonazzo, vinicius
Target Milestone: ovirt-4.4.3Keywords: Triaged, ZStream
Target Release: 4.4.3   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: ovirt-hosted-engine-setup-2.4.7-3.el8ev Doc Type: Release Note
Doc Text:
Ansible-2.9.14 is required for proper setup and functioning of Red Hat Virtualization Manager 4.4.3.
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-11-24 13:11:27 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Integration RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Martin Perina 2020-10-15 11:57:32 UTC
Bump requirements to ansible-2.9.14 in ovirt-hosted-engine-setup for RHV Manager 4.4.3

Comment 4 Sandro Bonazzola 2020-10-23 15:06:37 UTC
*** Bug 1891018 has been marked as a duplicate of this bug. ***

Comment 6 Nikolai Sednev 2020-10-26 11:14:00 UTC
New ovirt-hosted-engine-setup-2.4.7-3.el8ev.noarch comes with ansible-2.9.14-1.el8ae.noarch during installation.

Red Hat Enterprise Linux release 8.3 (Ootpa)
Linux 4.18.0-240.1.1.el8_3.x86_64 #1 SMP Fri Oct 16 13:36:46 EDT 2020 x86_64 x86_64 x86_64 GNU/Linux

Comment 12 errata-xmlrpc 2020-11-24 13:11:27 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 (RHV RHEL Host (ovirt-host) 4.4.z [ovirt-4.4.3]), 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/RHBA-2020:5213

Comment 13 Vinícius Ferrão 2020-11-24 18:14:11 UTC
It is now broken for Ansible 2.9.15...

[root@rhv ~]# dnf update
Updating Subscription Management repositories.
Last metadata expiration check: 2:23:09 ago on Tue 24 Nov 2020 12:44:58 PM -03.
Error:
 Problem: package ovirt-engine-4.4.3.12-0.1.el8ev.noarch requires ansible = 2.9.14, but none of the providers can be installed
  - cannot install both ansible-2.9.15-1.el8ae.noarch and ansible-2.9.14-1.el8ae.noarch
  - cannot install the best update candidate for package ovirt-engine-4.4.3.12-0.1.el8ev.noarch
  - cannot install the best update candidate for package ansible-2.9.14-1.el8ae.noarch
(try to add '--allowerasing' to command line to replace conflicting packages or '--skip-broken' to skip uninstallable packages or '--nobest' to use not only best candidate packages)

Comment 14 Martin Perina 2020-11-25 05:52:26 UTC
(In reply to Vinícius Ferrão from comment #13)
> It is now broken for Ansible 2.9.15...
> 
> [root@rhv ~]# dnf update
> Updating Subscription Management repositories.
> Last metadata expiration check: 2:23:09 ago on Tue 24 Nov 2020 12:44:58 PM
> -03.
> Error:
>  Problem: package ovirt-engine-4.4.3.12-0.1.el8ev.noarch requires ansible =
> 2.9.14, but none of the providers can be installed
>   - cannot install both ansible-2.9.15-1.el8ae.noarch and
> ansible-2.9.14-1.el8ae.noarch
>   - cannot install the best update candidate for package
> ovirt-engine-4.4.3.12-0.1.el8ev.noarch
>   - cannot install the best update candidate for package
> ansible-2.9.14-1.el8ae.noarch
> (try to add '--allowerasing' to command line to replace conflicting packages
> or '--skip-broken' to skip uninstallable packages or '--nobest' to use not
> only best candidate packages)

Yes, that's correct, ovirt-hosted-engine-setup and ovirt-engine packages are always locked on specific ansible version, which has been properly tested. From version 4.4.2 you need to use "--nobest" options when executing "dnf upgrade" commands

Comment 15 meital avital 2022-08-08 19:38:32 UTC
Due to QE capacity, we are not going to cover this issue in our automation