Bug 960314

Summary:	autoinstall RHN registration shows package updates
Product:	Red Hat Enterprise Linux 6	Reporter:	Joey Boggs <jboggs>
Component:	ovirt-node	Assignee:	Joey Boggs <jboggs>
Status:	CLOSED ERRATA	QA Contact:	Virtualization Bugs <virt-bugs>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	6.4	CC:	acathrow, bsarathy, cboyle, huiwa, jboggs, leiwang, mburns, ovirt-maint, ycui
Target Milestone:	rc
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	ovirt-node-3.0.0-6.el6	Doc Type:	Bug Fix
Doc Text:	Using auto install hypervisor registration showed package updates. This was because when registering the hypervisor to the Red Hat Network, the package list would be sent and possible updates would be shown in the Red Hat Network page, rather than leaving those details out. Affected hypervisor nodes would show as having possible single rpm package updates when they would not be applicable. The hypervisor Red Hat Network registration now skips the package update in the profile. The registration now works without package lists being compared for updates.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2014-01-21 19:33:16 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	913579
Bug Blocks:

Description Joey Boggs 2013-05-07 02:23:50 UTC

Description of problem:
When autoinstalling and registering to RHN or satellite possible updates will be be shown when they shouldn't be. When performing a manual install and registration the problem does not appear


Steps to Reproduce:
1. Auto install registering RHN/Satellite at the same time
2. Check system in RHN/Satellite and see that package updates are available

Expected results:
Updates will not be shown

Comment 5 wanghui 2013-10-22 09:40:32 UTC

There is a bug#1020774 in rhev-hypervisor6-6.5-20131017.0 which is blocking the testing of this bug. So I will wait the fix of bug#1020774.

Comment 7 Cheryn Tan 2013-11-08 00:25:35 UTC

This bug is currently attached to errata RHBA-2013:15277. If this change is not to be documented in the text for this errata please either remove it from the errata, set the requires_doc_text flag to minus (-), or leave a "Doc Text" value of "--no tech note required" if you do not have permission to alter the flag.

Otherwise to aid in the development of relevant and accurate release documentation, please fill out the "Doc Text" field above with these four (4) pieces of information:

* Cause: What actions or circumstances cause this bug to present.
* Consequence: What happens when the bug presents.
* Fix: What was done to fix the bug.
* Result: What now happens when the actions or circumstances above occur. (NB: this is not the same as 'the bug doesn't present anymore')

Once filled out, please set the "Doc Type" field to the appropriate value for the type of change made and submit your edits to the bug.

For further details on the Cause, Consequence, Fix, Result format please refer to:

https://bugzilla.redhat.com/page.cgi?id=fields.html#cf_release_notes 

Thanks in advance.

Comment 10 errata-xmlrpc 2014-01-21 19:33:16 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.

http://rhn.redhat.com/errata/RHBA-2014-0033.html