Hide Forgot
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.
Fixed in master in b04de4d516d9f6b1036248db29c23a7b1e577c97. New string is "Subscription pool {0} does not exist.
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
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