Bug 956298
| Summary: | subscription-manager fails when no org is passed, man page states it should work | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 5 | Reporter: | Joe Ceresini <jceresini> |
| Component: | subscription-manager | Assignee: | Deon Ballard <dlackey> |
| Status: | CLOSED ERRATA | QA Contact: | IDM QE LIST <seceng-idm-qe-list> |
| Severity: | medium | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 5.10 | CC: | bkearney, fsharath, jgalipea |
| Target Milestone: | rc | ||
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: |
No description necessary
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2013-09-30 23:06:58 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | |||
| Bug Blocks: | 840995 | ||
This request was evaluated by Red Hat Product Management for inclusion in a Red Hat Enterprise Linux release. Product Management has requested further review of this request by Red Hat Engineering, for potential inclusion in a Red Hat Enterprise Linux release for currently deployed products. This request is not yet committed for inclusion in a release. This is correct. You need to provide an org for activation keys. this is a man page change then. Assigning to deon. Version:
Brew Build
# subscription-manager version
server type: Red Hat Subscription Management
subscription management server: 0.8.7-1
subscription-manager: 1.8.8-1.el5
python-rhsm: 1.8.11-1.el5_9
Verification:
--activationkey=KEYS
Gives a comma-separated list of product keys to use to redeem or apply specific subscriptions to the system. This is used for preconfigured systems, which may already have
products installed and subscriptions attached to that system. Activation keys are issued by an on-premise subscription management service, such as Subscription Asset Manager.
When the --activationkey option is used, it is not necessary to use the --username and --password options, because the authentication information is implicit in the activation
key.
For example:
subscription-manager register --org="IT Dept" --activationkey=1234abcd
The above is updated man page for "subscription-manager" -> "register options" -> "--activation-key"
It no longer mentions "When there is a single organization or when using the Customer Portal Subscription Management service, it is not necessary to specify an organization with the --org option, but in multi-organization environments, this is required" as before
refer https://bugzilla.redhat.com/show_bug.cgi?id=956285#c0
VERIFIED
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHBA-2013-1332.html |
Description of problem: man page states that no org is required when using activation keys if there is only 1 org, or if you use Customer Portal Subscription Management ------------------------------------ When there is a single organization or when using the Customer Portal Subscription Management service, it is not necessary to specify an organization with the --org option, but in multi- organization environments, this is required. ------------------------------------ but not passing an org results in an error: $ subscription-manager register --activationkey xxxxxxxxx Error: Must provide --org with activation keys. Version-Release number of selected component (if applicable): subscription-manager: 1.1.23-1.el6 python-rhsm: 1.1.8-1.el6 How reproducible: Happens every time Steps to Reproduce: 1. Run subscription-manager as described above with valid activationkey and no org 2. Get error message listed above Actual results: System is unregistered Expected results: No error message, system registered Additional info: We are using the Customer Portal, not our own SAM installation