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.
Bug 725242 - wording on "No such entitlement pool" message
Summary: wording on "No such entitlement pool" message
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: subscription-manager
Version: 6.2
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: rc
: ---
Assignee: Bryan Kearney
QA Contact: John Sefler
URL:
Whiteboard:
Depends On:
Blocks: rhsm-rhel62
TreeView+ depends on / blocked
 
Reported: 2011-07-24 15:28 UTC by John Sefler
Modified: 2011-12-06 17:22 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-12-06 17:22:43 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2011:1695 0 normal SHIPPED_LIVE subscription-manager bug fix and enhancement update 2011-12-06 01:23:29 UTC

Description John Sefler 2011-07-24 15:28:02 UTC
Description of problem:
When attempting to subscribe to a pool that does not exist, the error message is:
No such entitlement pool: 123

I believe this is the only place the term "entitlement pool" is used.  Most everywhere else we have called it a "subscription pool".

A more consistent error message would be:
Subscription pool '123' does not exist.


Version-Release number of selected component (if applicable):
# rpm -q subscription-manager
subscription-manager-0.96.4-1.git.54.5de26be.el6.x86_64


Steps to Reproduce:
# subscription-manager subscribe --pool=123
  
Actual results:
No such entitlement pool: 123

Expected results:
Subscription pool '123' does not exist.

Comment 1 Bryan Kearney 2011-07-26 18:27:56 UTC
Fixed in master in b04de4d516d9f6b1036248db29c23a7b1e577c97. New string is "Subscription pool {0} does not exist.

Comment 3 John Sefler 2011-07-26 21:09:29 UTC
Verifying Version...
[root@jsefler-onprem-62candlepin proxy]# git branch
  0.3
* master
[root@jsefler-onprem-62candlepin proxy]# git show-ref | grep master
b04de4d516d9f6b1036248db29c23a7b1e577c97 refs/heads/master
b04de4d516d9f6b1036248db29c23a7b1e577c97 refs/remotes/origin/master


[root@jsefler-onprem-62server ~]# subscription-manager register --username=testuser1 --password=password --org=admin
The system has been registered with id: 9175510f-410a-4e2a-8519-3c38fb8ad017 
[root@jsefler-onprem-62server ~]# subscription-manager subscribe --pool=123
Subscription pool 123 does not exist.
[root@jsefler-onprem-62server ~]# 

moving to VERIFIED

Comment 4 errata-xmlrpc 2011-12-06 17:22:43 UTC
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-2011-1695.html


Note You need to log in before you can comment on or make changes to this bug.