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.
DescriptionShwetha Kallesh
2016-01-14 13:45:00 UTC
Description of problem:
When you try to remove a pool that is not found no message/feedback is thrown to the user
Version-Release number of selected component (if applicable):
[root@dhcp35-189 ~]# subscription-manager version
server type: Red Hat Subscription Management
subscription management server: 2.0.10-1
subscription management rules: 5.19
subscription-manager: 1.16.7-1.el6
python-rhsm: 1.16.5-1.el6
How reproducible:
Steps to Reproduce:
when you provide invalid poolids along with invalid serial number , no message is thrown for invalid pool :
[root@dhcp35-189 ~]# subscription-manager remove --pool 8ac6a3f45215de5a015215dfb790073a --serial 5716740667283576794
Serial numbers unsuccessfully removed at the server:
5716740667283576794
when you provide invalid poolids , no message is thrown for invalid pool :
[root@dhcp35-189 ~]# subscription-manager remove --pool 8ac6a3f45215de5a015215dfb790073a --pool 8ac6a3f45215de5a015215dfb3ea06d6
Actual results:
No message
Expected results:
should say something similar to " Pool '<poolid>' was not found."
Additional info:
In upstream master as of the following commit:
commit e418b77ce2a7389e310ac341a6beb46cb7eb3d0f
Author: William Poteat <wpoteat>
Date: Mon Jan 18 13:22:15 2016 -0500
1298586: Message needed for remove only invalid pool
This will be included in the next build (set to be completed today) before devel-freeze. As such I am moving this BZ to the modified state.
I see the message for the invalid pool removal , hence moving bug to verified :
[root@hp-dl320egen8-01 ~]# subscription-manager version
server type: Red Hat Subscription Management
subscription management server: 2.0.10-1
subscription management rules: 5.19
subscription-manager: 1.16.8-1.el6
python-rhsm: 1.16.6-1.el6
[root@hp-dl320egen8-01 ~]# subscription-manager remove --pool 8ac6a3f45215de5a015215dfb790073a --pool 8ac6a3f45215de5a015215dfb3ea06d6
Pools unsuccessfully removed at the server:
8ac6a3f45215de5a015215dfb790073a
8ac6a3f45215de5a015215dfb3ea06d6
[root@hp-dl320egen8-01 ~]# subscription-manager remove --pool 8ac6a3f45215de5a015215dfb790073a --serial 5716740667283576794
Pools unsuccessfully removed at the server:
8ac6a3f45215de5a015215dfb790073a
Serial numbers unsuccessfully removed at the server:
5716740667283576794
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.
https://rhn.redhat.com/errata/RHBA-2016-0797.html