Bug 1458409 – [Tracking] rhvm-branding-rhv 4.2.3 for RHV 4.2

Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.

Bug 1458409 - [Tracking] rhvm-branding-rhv 4.2.3 for RHV 4.2

Summary:	[Tracking] rhvm-branding-rhv 4.2.3 for RHV 4.2

Status:	CLOSED ERRATA

Aliases:	None

Product:	Red Hat Enterprise Virtualization Manager
Classification:	Red Hat
Component:	rhvm-branding-rhv (Show other bugs)
Sub Component:
Version:	4.2.0
Hardware:	Unspecified Unspecified

Priority	unspecified Severity medium
Target Milestone:	ovirt-4.2.3
Target Release:	---
Assigned To:	Greg Sheremeta
QA Contact:	Pavol Brilla
Docs Contact:

URL:
Whiteboard:
Keywords:	Rebase, Tracking

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2017-06-02 14:55 EDT by Greg Sheremeta
Modified:	2018-05-15 13:32 EDT (History)
CC List:	5 users (show)

See Also:
Fixed In Version:
Doc Type:	No Doc Update
Doc Text:	undefined
Story Points:	---
Clone Of:
Environment:
Last Closed:	2018-05-15 13:31:29 EDT
Type:	Bug
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	UX
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

External Trackers
Tracker	ID	Priority	Status	Summary	Last Updated
Red Hat Product Errata	RHBA-2018:1466	None	None	None	2018-05-15 13:32 EDT

Groups: None (edit)

Description Greg Sheremeta 2017-06-02 14:55:55 EDT

[Tracking] rhvm-branding-rhv 4.2.0 for RHV 4.2

Comment 7 Greg Sheremeta 2018-05-01 13:31:39 EDT

bumped to 4.2.3-1

Comment 10 errata-xmlrpc 2018-05-15 13:31:29 EDT

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, 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-2018:1466

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