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

Bug 1874520

Summary: Require tested ansible-2.9.13 for RHV Manager 4.3.11
Product: Red Hat Enterprise Virtualization Manager Reporter: Martin Perina <mperina>
Component: ovirt-engineAssignee: Martin Perina <mperina>
Status: CLOSED ERRATA QA Contact: Petr Matyáš <pmatyas>
Severity: high Docs Contact:
Priority: high    
Version: 4.3.10CC: dfodor, lleistne, michal.skrivanek, mperina, pelauter, rdlugyhe
Target Milestone: ovirt-4.3.11-1Keywords: ZStream
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: rhvm-4.3.11.4-0.1 Doc Type: Release Note
Doc Text:
Previously, customers were having issues with asynchronous Ansible updates breaking installed RHV setups. The current release fixes this issue. RHV Manager 4.3.11 requires ansible-2.9.13. These have been tested and verified to work together.
 Story Points: ---
Clone Of: 1873041 Environment:
Last Closed: 2020-09-30 09:18:21 UTC Type: ---
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: 1873041    
Bug Blocks:    

Description Martin Perina 2020-09-01 14:27:04 UTC 
+++ This bug was initially created as a clone of Bug #1873041 +++

We have issues with async ansible updates breaking existing installed setups. We receive those by using a ansible-2.9-for-rhel-8-x86_64-rpms CDN on engine and hostst.

Easiest solution is to require a concrete version which was validated to work in ovirt-engine and ovirt-hosted-engine-setup. These two packages should be in sync.

It is acceptable that this won't work if anyone installs a later ansible version before deploying engine/host. We do not expect that to happen.

--- Additional comment from Michal Skrivanek on 2020-08-27 11:14:14 CEST ---

We need to push this live with a version which is
1) confirmed working ok
2) the last one available
to avoid an unpleasant surprise for someone who upgraded to latest ansible 2.9.X  before this change and then us requiring =2.9.X-1
We want to do this downstream only in order to get enough testing from oVirt using the upcoming versions

(not sure if we have to rush this to 4.4.2)

--- Additional comment from Sandro Bonazzola on 2020-08-28 17:42:36 CEST ---

(In reply to Michal Skrivanek from comment #1)
> We need to push this live with a version which is
> 1) confirmed working ok
> 2) the last one available
> to avoid an unpleasant surprise for someone who upgraded to latest ansible
> 2.9.X  before this change and then us requiring =2.9.X-1
> We want to do this downstream only in order to get enough testing from oVirt
> using the upcoming versions
> 
> (not sure if we have to rush this to 4.4.2)

I would consider targeting 4.4.3.
I've suspicion that if a new ansible is available and we force a specific version as dependency, either upgrade won't happen at all due to best candidate for ansible couldn't be installed or worst, ansible will get updated and engine won't because of unsatified dependency.
Comment 6 Petr Matyáš 2020-09-10 08:49:18 UTC 
Verified on ovirt-engine-4.3.11.4-0.1.el7.noarch
Comment 10 errata-xmlrpc 2020-09-30 09:18:21 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 (Red Hat Virtualization Engine security, bug fix 4.3.11 0-day), 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:4110