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.
DescriptionGarik Khachikyan
2013-05-28 09:12:35 UTC
Description of problem:
Right now the recent available option of RHSM seems does not allow to combine service level with activation keys during registration.
It is useful stuff to have different activation keys (with different usage limits) and with different RHEL subscriptions attached to them (recent implementation of Katello allows it) with different support levels there.
So one may want to expose it wishing to perform something like:
===
subscription-manager register --activationkey akTesting --release 6.4 --force --name awesomeSystem --org awesomeOrg --servicelevel Premium --auto-attach
===
it just gets fails with:
===
WARNING
This system has already been registered with Red Hat using RHN Classic.
The tool you are using is attempting to re-register using Red Hat Subscription Management technology. Red Hat recommends that customers only register once.
To learn how to unregister from either service please consult this Knowledge Base Article: https://access.redhat.com/kb/docs/DOC-45563
Error: Activation keys cannot be used with --auto-attach.
===
Version-Release number of selected component (if applicable):
subscription-manager-1.1.23.1-1.el6_4.x86_64
python-rhsm-1.8.0-1.pulp.el6sat.x86_64
How reproducible:
always
Steps to Reproduce:
1.Setup a Katello
2.manifest import + enable repo sets of RHEL6Server
3.promote to Testing env
4.prepare ak for Testing, set limit to 3, add the RHEL subscription from that manifest.
5.configure rhsm to connect to the Katello
6.perform the command above
Actual results:
failure
Expected results:
available to set servicelevel on registration using AKs
Additional info:
This must be run a separate commonads:
subscription-manager register --activationkey akTesting --release 6.4 --force --name awesomeSystem --org awesomeOrg
subscription-manager register --servicelevel Premium --auto-attach
These commands are mutually exclusive by design.