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.
Description of problem:
Fail to get "service_level_agreement" from /etc/rhsm/syspurpose/syspurpose.json after set service-level from satellite
Version-Release number of selected component (if applicable):
subscription-manager-1.29.18-1.el9.x86_64
subscription-manager-cockpit-1.29.18-1.el9.noarch
python3-subscription-manager-rhsm-1.29.18-1.el9.x86_64
subscription-manager-rhsm-certificates-1.29.18-1.el9.x86_64
tfm-rubygem-katello-4.1.0-1.el7sat.noarch
katello-4.1.0-1.el7sat.noarch
candlepin-4.0.5-1.el7sat.noarch
RHEL Compose: RHEL-9.0.0-20210721.3
Satellite6.10
How reproducible:
100%
Steps to Reproduce:
1.Register guest to satellite6.10
# subscription-manager register --username=admin --password=admin --org=Default_Organization --environment=Library
Registering to: intel-waimeabay-hedt-01.ml3.eng.bos.redhat.com:443/rhsm
The system has been registered with ID: ec3ca146-17c1-41b2-bf9a-f7a894ca930d
The registered system name is: dell-per430-03.gsslab.pek2.redhat.com
2. Set service-level on satellite by hammer
# hammer -u admin -p admin host update --id=64 --purpose-addons="High Availability"
Host updated.
3.Check service-level on satellite
json.tool
[root@dell-per430-03 ~]# curl -k -u admin:admin https://intel-waimeabay-hedt-01.ml3.eng.bos.redhat.com:443/rhsm/consumers/ec3ca146-17c1-41b2-bf9a-f7a894ca930d | python3 -mjson.tool
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 16755 0 16755 0 0 8649 0 --:--:-- 0:00:01 --:--:-- 8645
{
"created": "2021-07-26T03:46:56+0000",
"updated": "2021-07-26T03:47:53+0000",
"id": "8a9330a67ab02da9017ae0ec3d3f38cf",
"uuid": "ec3ca146-17c1-41b2-bf9a-f7a894ca930d",
"name": "dell-per430-03.gsslab.pek2.redhat.com",
"username": "foreman_admin",
"entitlementStatus": "invalid",
"serviceLevel": "Self-Support",
"role": "",
"usage": "",
"addOns": [],
4. Check syspurpose service-level --show
# subscription-manager syspurpose service-level --show
Current service level: Self-Support
5. Check service-level in /syspurpose.json
# cat /etc/rhsm/syspurpose/syspurpose.json
{}
There is no service-level values in /syspurpose.json
Actual results:
Fail to get "service_level_agreement" from /etc/rhsm/syspurpose/syspurpose.json after set service-level from satellite
Expected results:
It should get "service_level_agreement" from /etc/rhsm/syspurpose/syspurpose.json after set service-level from satellite, as follow:
# cat /etc/rhsm/syspurpose/syspurpose.json
{
"service_level_agreement": "Self-Support"
}
Additional info:
(In reply to yanpliu from comment #1)
> 1. Upgrade sub-man throw error "libjson-c.so.5(JSONC_0.14)(64bit) is needed
> by libdnf-plugin-subscription-manager-1.29.21-1.el9.x86_64", after I install
> the libjson-c.so.5, it still has this issue. so I upgrade the sub-man
> packages with --nodeps, but I am not sure if this installation will affect
> the function or not.
Yes, this is expected, see also bug 2023321. The new build automatically uses the new library version, so that means it bumps the requirement.
Hence, please do *not* use --nodeps, which is in 99% of the cases (here included) a bad idea.
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 (new packages: subscription-manager), 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-2022:3984