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
2019-03-29 14:27:30 UTC
Description of problem:
repackage syspurpose for rhel7.7 as subscription-manager role,usage,service-level function is broken
Version-Release number of selected component (if applicable):
[root@kvm-04-guest11 ~]# subscription-manager version
server type: This system is currently not registered.
subscription management server: 2.3.15-1
subscription management rules: 5.34
subscription-manager: 1.24.3-1.el7
How reproducible:
Steps to Reproduce:
Service-level is broken:
-------------------------------------------------------------
[root@kvm-04-guest11 ~]# subscription-manager register --username shwetha_tier1_test
Registering to: subscription.rhsm.stage.redhat.com:443/subscription
Password:
The system has been registered with ID: 99ab7acf-d483-4ba3-9038-33a62a0100a7
The registered system name is: kvm-04-guest11.rhts.eng.bos.redhat.com
[root@kvm-04-guest11 ~]# subscription-manager service-level --set Premium
service_level_agreement set to "Premium".
[root@kvm-04-guest11 ~]# subscription-manager service-level --show
Service level preference not set
Role is broken
------------------------------------------------------------
[root@kvm-04-guest11 ~]# subscription-manager role --set foo
role set to "foo".
[root@kvm-04-guest11 ~]# subscription-manager role
Role not set.
No syspurpose.json file
-------------------------------------
root@kvm-04-guest11 ~]# ls /etc/rhsm/
ca/ facts/ logging.conf pluginconf.d/ rhsm.conf
Actual results:
Expected results:
Additional info:
Verifying Version...
[root@amd-pike-06 ~]# rpm -q subscription-manager
subscription-manager-1.24.4-1.el7.x86_64
[root@amd-pike-06 ~]# rpm -q subscription-manager --requires | grep syspurpose
python-syspurpose
[root@amd-pike-06 ~]# rpm -q python-syspurpose
python-syspurpose-1.24.4-1.el7.x86_64
[root@amd-pike-06 ~]#
[root@amd-pike-06 ~]#
[root@amd-pike-06 ~]#
[root@amd-pike-06 ~]# subscription-manager role
Role not set.
[root@amd-pike-06 ~]#
[root@amd-pike-06 ~]# subscription-manager role --set "Red Hat Enterprise Linux Server"
role set to "Red Hat Enterprise Linux Server".
[root@amd-pike-06 ~]#
[root@amd-pike-06 ~]# subscription-manager role
Current Role: Red Hat Enterprise Linux Server
[root@amd-pike-06 ~]#
[root@amd-pike-06 ~]#
[root@amd-pike-06 ~]# syspurpose show
{
"role": "Red Hat Enterprise Linux Server"
}
Unable to send system purpose to subscription management server
[root@amd-pike-06 ~]#
VERIFIED: subscription-manager-1.24.4-1.el7 now requires python-syspurpose which enables the syspurpose attributes like role to be set.
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-2019:2008