Bug 732433

Summary: Doc has incorrect instructions regarding RHN registration
Product: Red Hat Enterprise Linux 6 Reporter: Andrew Cathrow <acathrow>
Component: DocumentationAssignee: Stephen Gordon <sgordon>
Status: CLOSED NEXTRELEASE QA Contact: ecs-bugs
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 6.2CC: apevec, cpelland, cshao, gouyang, jskeoch, kli, mburns, moli, rbalakri, ycui
Target Milestone: rcKeywords: Documentation
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Red_Hat_Enterprise_Linux-Hypervisor_Deployment_Guide-6-web-en-US-1-31.el6eng Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-10-31 01:07:32 UTC Type: ---
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:    
Bug Blocks: 617060, 728234    

Description Andrew Cathrow 2011-08-22 13:06:07 UTC
The following text is wrong.

The Hypervisor is able to retrieve security updates from either the Red Hat Network or a Satellite server. Where necessary the Hypervisor is also able to connect to the remote updates server via a HTTP proxy.


RHEV-H cannot be updated via RHN.
The only use of RHN registration is to allow guests to consume RHEL virtualization entitlements (the legacy RHEL-5 virt and virt-platform entitlements)

We need to clarify this and stress that the node does NOT need to be registered to RHN.