Bug 1898024 - Rebase RHV-H 4.4.3 on RHGS-3.5.z Batch #3
Summary: Rebase RHV-H 4.4.3 on RHGS-3.5.z Batch #3
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: redhat-virtualization-host
Version: 4.4.3
Hardware: Unspecified
OS: Unspecified
high
medium
Target Milestone: ovirt-4.4.3-2
: 4.4.3
Assignee: Asaf Rachmani
QA Contact: cshao
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-11-16 07:39 UTC by Sandro Bonazzola
Modified: 2020-12-17 09:01 UTC (History)
10 users (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-12-17 09:00:27 UTC
oVirt Team: Node
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2020:5611 0 None None None 2020-12-17 09:01:14 UTC

Description Sandro Bonazzola 2020-11-16 07:39:58 UTC 
Rebase RHV-H 4.4.3 on RHGS-3.5.z Batch #3
Comment 3 Casper (RHV QE bot) 2020-11-16 16:02:00 UTC 
This bug has a low overall severity and passed automated regreession suite, it is not going to be further verified by QE. If you believe a special care is required feel free to re-open to ON_QA status
Comment 5 Sandro Bonazzola 2020-11-16 16:25:12 UTC 
Closed by mistake.
Comment 9 cshao 2020-12-01 11:58:34 UTC 
Test version:
redhat-virtualization-host-4.4.3-20201130.0.el8_3
glusterfs-6.0-49.el8rhgs.x86_64

RHVH include the correct RHGS version, so the bug is fixed, change bug status to VERIFIED.
Comment 11 errata-xmlrpc 2020-12-17 09:00: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 (Important: Red Hat Virtualization security, bug fix, and enhancement 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-2020:5611
Note You need to log in before you can comment on or make changes to this bug.