Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite 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 "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. 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 "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-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.
Description of problem:
auto-attach ignores invalid service level against satellite6.2
Version-Release number of selected component (if applicable):
subscription-manager: 1.17.8-1.el7
python-rhsm: 1.17.4-1.el7
Satellite-6.2.0-RHEL-7.2-20160629.1
How reproducible:
always
Steps to Reproduce:
1. Register RHEL-7.3-20160629.n.0 to Satellite-6.2.0-RHEL-7.2-20160629.1, and auto-attach by specifying a wrong service level:
[root@dhcp-128-18 ~]# subscription-manager register --username=admin --password=admin --org=Default_Organization --servicelevel=foo --auto-attach
Registering to: hp-dl2x170g6-02.rhts.eng.bos.redhat.com:443/rhsm
The system has been registered with ID: b67a62ed-b658-44f9-a738-8862ab6a2b1d
Service level set to: foo
Installed Product Current Status:
Product Name: Red Hat Enterprise Linux Server
Status: Subscribed
2. [root@dhcp-128-18 ~]# subscription-manager service-level --show
Service level preference not set
3. [root@dhcp-128-18 ~]# subscription-manager service-level --list
+-------------------------------------------+
Available Service Levels
+-------------------------------------------+
Basic
Premium
Self-Support
Standard
Actual results:
As step 1, auto-attach succeeds with wrong sevice level.
Expected results:
auto-attach should fail with warning like below:
# subscription-manager register --username=admin --org=ACME_Corporation --servicelevel=foo --auto-attach
Registering to: samserv.redhat.com:443/sam/api
Password:
The system has been registered with ID: 002c1477-18a4-41b4-9412-e315ffa221de
Service level 'foo' is not available to units of organization ACME_Corporation.
Installed Product Current Status:
Product Name: Red Hat Enterprise Linux Server
Status: Not Subscribed
Unable to find available subscriptions for all your installed products.
Additional info:
The attachment is rhsm.log
When the registration is complete in the first step, then the next step is for the service level to be set.
Without Katello in the middle, the REST exception [BadRequestException] message surfaces when the service level is not available.
Somewhere Katello is absorbing the exception here. Sub Man just assumes the service level was set because no exception was returned. Katello must allow it to pass for Sub Man to know how to behave.
Thank you for your interest in Satellite 6. We have evaluated this request, and we do not expect this to be implemented in the product in the forseeable future. We are therefore closing this out as WONTFIX. If you have any concerns about this, please feel free to contact Rich Jerrido or Bryan Kearney. Thank you.
Description of problem: auto-attach ignores invalid service level against satellite6.2 Version-Release number of selected component (if applicable): subscription-manager: 1.17.8-1.el7 python-rhsm: 1.17.4-1.el7 Satellite-6.2.0-RHEL-7.2-20160629.1 How reproducible: always Steps to Reproduce: 1. Register RHEL-7.3-20160629.n.0 to Satellite-6.2.0-RHEL-7.2-20160629.1, and auto-attach by specifying a wrong service level: [root@dhcp-128-18 ~]# subscription-manager register --username=admin --password=admin --org=Default_Organization --servicelevel=foo --auto-attach Registering to: hp-dl2x170g6-02.rhts.eng.bos.redhat.com:443/rhsm The system has been registered with ID: b67a62ed-b658-44f9-a738-8862ab6a2b1d Service level set to: foo Installed Product Current Status: Product Name: Red Hat Enterprise Linux Server Status: Subscribed 2. [root@dhcp-128-18 ~]# subscription-manager service-level --show Service level preference not set 3. [root@dhcp-128-18 ~]# subscription-manager service-level --list +-------------------------------------------+ Available Service Levels +-------------------------------------------+ Basic Premium Self-Support Standard Actual results: As step 1, auto-attach succeeds with wrong sevice level. Expected results: auto-attach should fail with warning like below: # subscription-manager register --username=admin --org=ACME_Corporation --servicelevel=foo --auto-attach Registering to: samserv.redhat.com:443/sam/api Password: The system has been registered with ID: 002c1477-18a4-41b4-9412-e315ffa221de Service level 'foo' is not available to units of organization ACME_Corporation. Installed Product Current Status: Product Name: Red Hat Enterprise Linux Server Status: Not Subscribed Unable to find available subscriptions for all your installed products. Additional info: The attachment is rhsm.log