Bug 1873041 - Require tested ansible-2.9.13 for RHV Manager 4.4.2
Summary: Require tested ansible-2.9.13 for RHV Manager 4.4.2
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-engine
Version: 4.4.1
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ovirt-4.4.2
: ---
Assignee: Martin Perina
QA Contact: Lucie Leistnerova
URL:
Whiteboard:
Depends On:
Blocks: 1873049 1873055 1874520
TreeView+ depends on / blocked
 
Reported: 2020-08-27 08:39 UTC by Michal Skrivanek
Modified: 2020-09-23 16:12 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
Clone Of:
: 1873049 1874520 (view as bug list)
Environment:
Last Closed: 2020-09-23 16:12:20 UTC
oVirt Team: Infra
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1815439 1 None None None 2023-09-14 05:54:33 UTC
Red Hat Product Errata RHBA-2020:3821 0 None None None 2020-09-23 16:12:31 UTC

Description Michal Skrivanek 2020-08-27 08:39:15 UTC
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.

Comment 7 errata-xmlrpc 2020-09-23 16:12:20 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 Manager (ovirt-engine) 4.4.z [ovirt-4.4.2] 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:3821


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