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.

Some new RHSM/candlepin features will require changes to the firstboot workflow. These features are:

1. Multi-org support
2. Stacking (multi-quantity entitlements)
3. Activation keys

Also, a lot of typos and errors were introduced into the content section of the firstboot chapter which need to be cleaned up.

Thanks Deon for supplying the content for fixing this.

Updates incorporated into build 1.0-42 of the guide:

http://documentation-stage.bne.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/6/html/Installation_Guide/sn-firstboot-updates.html

Specifically:

1. multi-organization support now discussed in http://documentation-stage.bne.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/6/html/Installation_Guide/firstboot-rhsm.html

2. stacking now discussed in http://documentation-stage.bne.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/6/html/Installation_Guide/firstboot-rhsmproducts.html

3. activation keys are within scope of the Installation Guide only in the context of using them during installation -- that is, using them in a kickstart file with rhnreg_ks. An example of doing this is provided in "Example 32.1.  Register the system to a Red Hat Network Satellite and log the output:"

http://documentation-stage.bne.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/6/html/Installation_Guide/s1-kickstart2-postinstallconfig.html#s2-kickstart2-post-examples

(Note to QE -- see also: https://access.redhat.com/kb/docs/DOC-2395 )

Rudi

Hi Andrew - you're right, that is too inconsistent with the previous screenshot and the accompanying text.

Due to the time constraints we're under, I've had to comment out the image for now and leave the step as text-only. 

I'll push this bug to 6.3. Hopefully we can locate the original, otherwise I'll make a new image.