Bug 2072645 - Build and distribute python38-pexpect in RHV channels
Summary: Build and distribute python38-pexpect in RHV channels
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: distribution
Version: unspecified
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ovirt-4.5.0
: ---
Assignee: Martin Perina
QA Contact: Pavol Brilla
URL:
Whiteboard:
Depends On:
Blocks: 2065052
TreeView+ depends on / blocked
 
Reported: 2022-04-06 17:09 UTC by Martin Perina
Modified: 2022-05-26 16:24 UTC (History)
5 users (show)

Fixed In Version: python3-pexpect-4.7.0-4.3.el8ev, python38-pexpect-4.7.0-4.3.el8ev
Doc Type: Rebase: Bug Fixes and Enhancements
Doc Text:
python3-pexpect/python38-pexpect are runtime dependencies for several Red Hat Virtualization Manager components. They need to be provided in the RHEL-8-RHEV-S-4.4 channel
Clone Of:
Environment:
Last Closed: 2022-05-26 16:24:18 UTC
oVirt Team: Infra
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHV-45561 0 None None None 2022-04-06 18:53:42 UTC
Red Hat Product Errata RHSA-2022:4711 0 None None None 2022-05-26 16:24:28 UTC

Description Martin Perina 2022-04-06 17:09:56 UTC 
ansible-core-2.12 requires all libraries used in Ansible modules/roles/playbooks to be built with Python 3.8, so we need to build and distribute python38-pexpect in RHV channels, because it's a dependency ansible-runner, which is required by RHV Manager
Comment 9 errata-xmlrpc 2022-05-26 16:24:18 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 (Moderate: RHV Manager (ovirt-engine) [ovirt-4.5.0] security update), 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/RHSA-2022:4711
Note You need to log in before you can comment on or make changes to this bug.