Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 754363

Summary: In chapter 3.1, the Entitlements channel name & label name are not exact.
Product: Red Hat Enterprise Linux 6 Reporter: Ying Cui <ycui>
Component: DocumentationAssignee: Laura Bailey <lbailey>
Status: CLOSED DUPLICATE QA Contact: ecs-bugs
Severity: medium Docs Contact:
Priority: medium    
Version: 6.2CC: apevec, cshao, gouyang, kli, leiwang, mburns, moli
Target Milestone: rcKeywords: Documentation
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-11-16 11:02:47 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:
Attachments:
Description Flags
snapshot for this bug none

Description Ying Cui 2011-11-16 09:33:03 UTC
http://documentation-stage.bne.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/6-Beta/html/Hypervisor_Deployment_Guide/chap-Deployment_Guide-Preparing_Red_Hat_Enterprise_Virtualization_Hypervisor_installation_media.html

In chapter 3.1, the Entitlements channel name & label name are not very exact.

In guide:
Entitlements to the Red Hat Enterprise Virtualization Hypervisor (v.6 x86-64) channel must be available on your Red Hat Network account to download the Hypervisor image. The channel's label is rhel-x86_64-server-6-rhevh.

Beta releases of the Red Hat Enterprise Virtualization Hypervisor are distributed using an alternative channel. Beta releases consist of pre-release software. They must not be used in a production environment.
The channel required to obtain beta releases of the Red Hat Enterprise Virtualization Hypervisor is the Red Hat Enterprise Virtualization Hypervisor Beta (v.6 x86-64) channel, also referred to by the identifier rhel-x86_64-server-6-rhevh-beta in Red Hat Network. 


Actual in RHN, there the entitlement channel name is : Red Hat Enterprise Virtualization Hypervisor Beta (for v6 Server) and the label name is : rhev-x86_64-h-6-beta
https://rhn.redhat.com/network/software/channels/details.pxt?cid=12059

Comment 1 Ying Cui 2011-11-16 09:34:38 UTC
Created attachment 533945 [details]
snapshot for this bug

Comment 3 Guohua Ouyang 2011-11-16 11:02:47 UTC
https://bugzilla.redhat.com/show_bug.cgi?id=754032#c3

according to above comment, the label will be rhev-x86_64-h-6 when 6.2 goes GA.

*** This bug has been marked as a duplicate of bug 754032 ***