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.
Bug 2215071 - SLA that is passed during register with --auto-attach is ignored/not set on the system
Summary: SLA that is passed during register with --auto-attach is ignored/not set on t...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: subscription-manager
Version: 7.9
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: CSI Client Tools Bugs
QA Contact: Red Hat subscription-manager QE Team
URL:
Whiteboard:
Depends On: 1838413
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-06-14 16:09 UTC by John Sefler
Modified: 2023-06-27 10:06 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1838413
Environment:
Last Closed: 2023-06-27 10:06:38 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHELPLAN-159882 0 None None None 2023-06-14 16:10:49 UTC

Comment 2 John Sefler 2023-06-14 16:30:21 UTC
I cloned this bug which was fixed in RHEL-8 back to RHEL-7 because recent automated testruns for the benefit of RHEL7.9z revealed that this issue also applies to subscription-manager on RHEL-7.9...

Here's a manual demonstration showing the failure...

[root@kvm-01-guest07 ~]# rpm -q subscription-manager
subscription-manager-1.24.51+27.g071c73f61-1.git.0.5e3b669.x86_64

[root@kvm-01-guest07 ~]# subscription-manager service-level --list --org=16769664 --username=stage_rhsmqe_testuser01 --password=REDACTED
+-------------------------------------------+
               Available Service Levels
+-------------------------------------------+
AMC-Enhanced
Premium
Self-Support
Standard
[root@kvm-01-guest07 ~]# 
[root@kvm-01-guest07 ~]# subscription-manager register --org=16769664 --username=stage_rhsmqe_testuser01 --servicelevel=Premium --auto-attach
Registering to: subscription.rhsm.stage.redhat.com:443/subscription
Password: 
The system has been registered with ID: dfed52b3-0777-4b1c-87bb-7eb6a0f772ad
The registered system name is: kvm-01-guest07.lab.eng.rdu2.redhat.com
Installed Product Current Status:
Product Name: Red Hat Enterprise Linux Server
Status:       Subscribed

[root@kvm-01-guest07 ~]# subscription-manager service-level --show
Service level preference not set
[root@kvm-01-guest07 ~]#


Actual Results:
  Service level preference not set

Expected Results:
  Current service level: Premium

Comment 3 Rehana 2023-06-27 10:06:38 UTC
Based on the discussion with Dev and QE teams, closing this bug as wont fix.


Note You need to log in before you can comment on or make changes to this bug.