Bug 1510727
| Summary: | The subscription-manager gui could not be launched after delete the consumer info from the server side | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | Wei Liu <weiliu> | ||||
| Component: | subscription-manager | Assignee: | Jiri Hnidek <jhnidek> | ||||
| Status: | CLOSED ERRATA | QA Contact: | Red Hat subscription-manager QE Team <rhsm-qe> | ||||
| Severity: | low | Docs Contact: | |||||
| Priority: | high | ||||||
| Version: | 7.5 | CC: | csnyder, jhnidek, jsefler, khowell, qianzhan, salmy, skallesh, weiliu | ||||
| Target Milestone: | rc | Keywords: | Regression, Triaged | ||||
| Target Release: | --- | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | subscription-manager-1.20.9-1 | Doc Type: | No Doc Update | ||||
| Doc Text: |
undefined
|
Story Points: | --- | ||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2018-04-10 09:52:44 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: | 1444512 | ||||||
| Attachments: |
|
||||||
|
Description
Wei Liu
2017-11-08 05:27:38 UTC
*** Bug 1511804 has been marked as a duplicate of this bug. *** Hi Chris Today I did the same operations on build RHEL-7.4-20170711.0 [root@dhcp-129-165 ~]# subscription-manager version server type: Red Hat Subscription Management subscription management server: 2.0.43-1 subscription management rules: 5.26 subscription-manager: 1.19.21-1.el7 python-rhsm: 1.19.9-1.el7 [root@dhcp-129-165 ~]# subscription-manager register Registering to: subscription.rhsm.stage.redhat.com:443/subscription Username: rnew_test Password: The system has been registered with ID: e944756a-0450-4396-bd29-7b144496ea9d [root@dhcp-129-165 ~]# subscription-manager identity system identity: e944756a-0450-4396-bd29-7b144496ea9d name: dhcp-129-165.nay.redhat.com org name: 11367791 org ID: 11367791 [root@dhcp-129-165 ~]# curl -k -u rnew_test:redhat --request DELETE https://subscription.rhsm.stage.redhat.com:443/subscription/consumers/e944756a-0450-4396-bd29-7b144496ea9d [root@dhcp-129-165 ~]# subscription-manager-gui Finally the subscription-manager gui was launched successfully.So I think this is a regression. Thank you! weiliu Verifying version: [root@bkr-hv03-guest35 ~]# rpm -qa | egrep "rhsm|subscription" subscription-manager-initial-setup-addon-1.20.9-1.el7.x86_64 subscription-manager-rhsm-1.20.9-1.el7.x86_64 subscription-manager-gui-1.20.9-1.el7.x86_64 subscription-manager-rhsm-certificates-1.20.9-1.el7.x86_64 subscription-manager-1.20.9-1.el7.x86_64 Verification: 1.Register the system to server [root@bkr-hv03-guest35 ~]# subscription-manager register Registering to: subscription.rhsm.stage.redhat.com:443/subscription Username: rnew_test Password: The system has been registered with ID: f495a8b6-72ee-4625-8e77-b73b7a1672ac The registered system name is: bkr-hv03-guest35.dsal.lab.eng.bos.redhat.com 2.Try to open the subscription-manager gui by command line and it be launched successfully #subscription-manager-gui 3.Delete the consumer info from the server side [root@bkr-hv03-guest35 ~]# curl -k -u username:****** --request DELETE https://subscription.rhsm.stage.redhat.com:443/subscription/consumers/f495a8b6-72ee-4625-8e77-b73b7a1672ac 4.Try to launch the subscription-manager gui again.The gui was launched successfully and no error message was shown. As the subscription-manager gui was launched successfully after deleting the consumer info from the server side.So this issue is verified and move the status to "verified". *** Bug 1510759 has been marked as a duplicate of this bug. *** 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://access.redhat.com/errata/RHBA-2018:0681 |