Bug 1997073 - Rebase RHV-M Appliance on RHEL 8.6.0
Summary: Rebase RHV-M Appliance on RHEL 8.6.0
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: rhvm-appliance
Version: 4.5.0
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ovirt-4.5.0-1
: 4.5.0
Assignee: Sanja Bonic
QA Contact: Wei Wang
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-08-24 11:25 UTC by Sandro Bonazzola
Modified: 2022-06-07 15:23 UTC (History)
0 users

Fixed In Version:
Doc Type: Rebase: Bug Fixes and Enhancements
Doc Text:
Rebase RHV-M Appliance on RHEL 8.6
Clone Of:
Environment:
Last Closed: 2022-06-07 15:22:53 UTC
oVirt Team: Node
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHV-43105 0 None None None 2021-08-24 11:29:07 UTC
Red Hat Product Errata RHSA-2022:4931 0 None None None 2022-06-07 15:23:11 UTC

Description Sandro Bonazzola 2021-08-24 11:25:18 UTC 
Rebase RHV-M Appliance on RHEL 8.6.0
Comment 3 Wei Wang 2022-02-21 02:17:05 UTC 
Test with rhvm-appliance-4.5-20211114.0.el8ev.x86_64

# cat /etc/redhat-release
Red Hat Enterprise Linux release 8.6 Beta (Ootap)

QE will verify this bug until the right appliance build is coming.
Comment 4 Wei Wang 2022-03-21 07:49:43 UTC 
Test with the latest rhvm-appliance-4.5-20220318.0.el8ev.x86_64

# cat /etc/redhat-release 
Red Hat Enterprise Linux release 8.6 Beta (Ootpa)


bug is fixed, move it to "VERIFIED"
Comment 6 errata-xmlrpc 2022-06-07 15:22:53 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 Appliance (rhvm-appliance) security update [ovirt-4.5.0]), 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:4931
Note You need to log in before you can comment on or make changes to this bug.