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.
Laura, it looks good from virt-who perspective, but I'm not familiar with subscription-manager that well. It would be better if someone from Satellite6 team recheck it. Chris, can you take a look?
On the step "Create a virt-who configuration file", there should be an opening bracket ('[') in front of "libvirt]".
Everything looks good as far as subscription-manager goes.
It might be worth mentioning somewhere in there that running subscription-manager remove --all followed by subscription-manager attach --auto will not necessarily result in attaching to the same pools (the ones that were removed).
To list available subscriptions for system type virtual:
`subscription-manager list --avail --match-installed | grep 'Virtual' -B12'
The subscriptions listed here are those that match the installed products, are available, and are for virtual systems only.
Choose from those listed and attach using the pool id:
`subscription-manager attach --<POOL_ID_HERE>`
Output for the first command:
"
Subscription Name: Red Hat Enterprise Linux ES (Basic for Virtualization)
Provides: Red Hat Beta
Oracle Java (for RHEL Server)
Red Hat Enterprise Linux Server
SKU: -------
Pool ID: ------------------------------
Available: 40
Suggested: 1
Service Level: Basic
Service Type: L1-L3
Multi-Entitlement: No
Ends: 01/02/2017
System Type: Virtual
"
I have removed the SKU number and the Pool ID from the above output.
Output for the second command:
"
Successfully attached a subscription for: Red Hat Enterprise Linux ES (Basic for Virtualization)
"
With all changes requested made and all content now verified, changing status to verified. This content will be republished by the end of the month.
Laura