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.

Documentation Link
------------------
https://access.qa.redhat.com/documentation/en/red-hat-atomic-enterprise-platform/version-3.1/getting-started-guide/

Request for enhancement
-----------------------
The step that reads "Find the pool ID that provides Atomic Enterprise Platform and attach it:" is really useful only if you're already familiar with subscription-manager and its output. Any user unfamiliar with subscription-manager and its output would have to develop familiarity with the output before confidently and quickly locating the pool ID. The documentation can be improved in order to orient the reader.

A section of screen output should be included in the documentation. The screen output should contain mock examples of the pools to which the Red Hat 7 system should be subscribed in order to install Red Hat Atomic Enterprise.

Two pools are required in order to permit customers to have access to the subscriptions necessary to install Red Hat Atomic Enterprise: (1) Red Hat Atomic Enterprise Platform (this name might change before GA), and (2) RHEL Server. The document should provide contextual screen output that permits the reader to confidently and quickly locate the correct pool IDs.

inb4: Obviously, don't put the actual pool IDs in the document. Use a string of Xs or something instead of the ID itself.

This is a AEP bug which doesn't exist anymore. I am going to CLOSE this bug now as CLOSED-->NOTABUG.