Bug 1356805

Summary:	Missing Red Hat's GPG keys
Product:	Red Hat Enterprise Virtualization Manager	Reporter:	Huijuan Zhao <huzhao>
Component:	redhat-release-rhev-hypervisor	Assignee:	Ryan Barry <rbarry>
Status:	CLOSED ERRATA	QA Contact:	Huijuan Zhao <huzhao>
Severity:	high	Docs Contact:
Priority:	high
Version:	4.0.0	CC:	cshao, dfediuck, dguo, fdeutsch, gklein, jiawu, leiwang, lsurette, mgoldboi, rbarry, weiwang, yaniwang, ycui, ykaul, yzhao
Target Milestone:	ovirt-4.0.1
Target Release:	4.0.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	redhat-virtualization-host-4.0-20160714.3	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-08-23 21:13:00 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	Node	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Comment 1 Huijuan Zhao 2016-07-15 06:00:38 UTC

This bug is fixed on redhat-virtualization-host-4.0-20160714.3.

Test version:
redhat-virtualization-host-4.0-20160714.3
imgbased-0.7.2-0.1.el7ev.noarch
redhat-release-virtualization-host-4.0-0.20.el7.x86_64
redhat-virtualization-host-image-update-placeholder-4.0-0.20.el7.noarch

Test steps:
1. Install RHVH redhat-virtualization-host-4.0-20160714.3
2. Check the GPG keys
   # ls /etc/pki/rpm-pgp

Test results:
After step2, there are GPG keys:
ls /etc/pki/rpm-gpg/
RPM-GPG-KEY-redhat-beta  
RPM-GPG-KEY-redhat-legacy-former  
RPM-GPG-KEY-redhat-legacy-release  
RPM-GPG-KEY-redhat-legacy-rhx  
RPM-GPG-KEY-redhat-release


So this issue is fixed on redhat-virtualization-host-4.0-20160714.3, I will verify this bug once it is changed to ON_QA

Comment 5 Huijuan Zhao 2016-07-18 01:58:56 UTC

According to comment 1, I will change the status to VERIFIED

Comment 8 errata-xmlrpc 2016-08-23 21:13:00 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, 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://rhn.redhat.com/errata/RHBA-2016-1688.html