Hide Forgot
Description of problem: Add a period at the end of this sentence: No free entitlements are available for the pool with id 'abc123' Version-Release number of selected component (if applicable): [root@jsefler-onprem-62server ~]# rpm -q subscription-manager subscription-manager-0.96.2-1.git.31.702703f.el6.x86_64 How reproducible: Steps to Reproduce: 1. consume all of the entitlements from a pool 2. try to subscribe again Actual results: No free entitlements are available for the pool with id 'abc123' Expected results: No free entitlements are available for the pool with id 'abc123'.
Actually, the wording should be "from the pool" rather than "for the pool": Expected results: No free entitlements are available from the pool with id 'abc123'.
While we are working on the wording of messages, this one could use some improvements after subscribing to a poolid: # subscription-manager subscribe --pool=abc123 Actual results: Successfully subscribed the system to Pool abc123 Expected results: Successfully consumed a subscription from the pool with id 'abc123'.
Actually both phrases are more verbose than they need to be. One more try... Expected results: No free entitlements are available from pool 'abc123'. Successfully consumed a subscription from pool 'abc123'.
orig bug and comment#1 seem to be fixed in: commit 886f8834b9fef18d9eb645c99de752ac7ef280aa Author: Bryan Kearney <bkearney> Date: Fri Jul 22 12:39:29 2011 -0400 Add some periods to the end of error messages
Fixed in dd17ef3cf45bfc4a6174976d44a8d97ef48c8a50 in master.
Comment 1 has not been fixed yet.. RPM used: [root@tiger ~]# rpm -qa | grep subscription-manager subscription-manager-gnome-0.98.3-1.git.16.14460bc.el5_7 subscription-manager-firstboot-0.98.3-1.git.16.14460bc.el5_7 subscription-manager-migration-0.98.3-1.git.16.14460bc.el5_7 subscription-manager-0.98.3-1.git.16.14460bc.el5_7 steps to reproduce: [root@tiger ~]# subscription-manager subscribe --pool=8ac1411b33c50dab0133c50eaa7b078a Successfully consumed a subscription from the pool with id 8ac1411b33c50dab0133c50eaa7b078a [root@tiger ~]# subscription-manager subscribe --pool=8ac1411b33c50dab0133c50ea9dd0774 --quantity=3 No free entitlements are available for the pool with id '8ac1411b33c50dab0133c50ea9dd0774'.
Comment 1 has not been fixed yet. [root@dhcp201-166 pki]# subscription-manager subscribe --pool=0000000035856b280135856bf7cd044d --quantity=1 No free entitlements are available for the pool with id '0000000035856b280135856bf7cd044d'. RPM used: [root@dhcp201-166 pki]# rpm -qa | grep subscription-manager subscription-manager-gnome-0.99.8-1.el6.x86_64 subscription-manager-0.99.8-1.el6.x86_64 subscription-manager-migration-0.99.8-1.el6.x86_64 subscription-manager-debuginfo-0.99.8-1.el6.x86_64
Moving it back to new
Please try with a later version from master: /tmp/tito/x86_64/subscription-manager-0.99.8-1.git.23.7c48eb4.fc16.x86_64.rpm It should have the fixed string.
[root@jsefler-r63-server ~]# rpm -q subscription-manager subscription-manager-0.99.9-1.git.3.1501812.el6.x86_64 [root@jsefler-r63-server ~]# subscription-manager subscribe --pool abc123 No free entitlements are available for the pool with id 'abc123'. ^^^^ ^^^ "for" should be replaced with "from" "free" is probably a bad choice of words (just remove it) Moving it back to NEW
Verifying Version.... [root@jsefler-r63-server ~]# rpm -q subscription-manager subscription-manager-0.99.9-1.git.13.7cda7cd.el6.x86_64 # subscription-manager subscribe --pool 8a90f8143611c33f013611c4797b0456 --quantity 10 Successfully consumed a subscription from the pool with id 8a90f8143611c33f013611c4797b0456. # subscription-manager subscribe --pool 8a90f8143611c33f013611c4797b0456 No entitlements are available from the pool with id '8a90f8143611c33f013611c4797b0456'. Verified that the word "free" has been removed. Verified that the messages end in a period. Verified that entitlements come "from" a pool rather than "for" a pool. Note: It would be better to use single quotes around the pool id consistently. 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-2012-0804.html