Bug 1661414

Can you please retest with the latest build?

I have verified in the latest build : RHEL-8.0-20190116.n.0 BaseOS x86_64 

python3-subscription-manager-rhsm-1.23.8-14.el8.x86_64
subscription-manager-rhsm-certificates-1.23.8-14.el8.x86_64
dnf-plugin-subscription-manager-1.23.8-14.el8.x86_64
subscription-manager-1.23.8-14.el8.x86_64

katello-3.7.0-8.el7sat.noarch
tfm-rubygem-katello-3.7.0.42-2.el7sat.noarch
candlepin-2.4.8-1.el7.noarch

This issue still can reproduce.


[root@ibm-x3650m4-01-vm-15 ~]# subscription-manager register
Registering to: hp-nehalem-02.rhts.eng.bos.redhat.com:443/rhsm
Username: admin
Password: 
The system has been registered with ID: 6c02c6f3-e249-4a02-9e8b-723d96b82c8f
The registered system name is: ibm-x3650m4-01-vm-15.lab.eng.bos.redhat.com
[root@ibm-x3650m4-01-vm-15 ~]# subscription-manager service-level --set=Self-Support
[root@ibm-x3650m4-01-vm-15 ~]# syspurpose show
{}
Unable to send system purpose to subscription management server
[root@ibm-x3650m4-01-vm-15 ~]# subscription-manager service-level --show
Current service level: Self-Support
[root@ibm-x3650m4-01-vm-15 ~]#  subscription-manager service-level --set=test
[root@ibm-x3650m4-01-vm-15 ~]# subscription-manager service-level --show
Current service level: Self-Support

Verification on RHEL-8.0.0-20190129.1 against Satellite6.4.1:
dnf-plugin-subscription-manager-1.23.8-14.el8.x86_64
python3-subscription-manager-rhsm-1.23.8-14.el8.x86_64
subscription-manager-1.23.8-14.el8.x86_64
subscription-manager-rhsm-certificates-1.23.8-14.el8.x86_64
candlepin-2.4.8-1.el7.noarch
tfm-rubygem-katello-3.7.0.42-2.el7sat.noarch


[root@ent-01-vm-01 ~]# subscription-manager register
Registering to: ent-01-vm-02.lab.eng.nay.redhat.com:443/rhsm
Username: admin
Password: 
The system has been registered with ID: 760847ff-f45d-4df9-a1a2-c5fc8853998e
The registered system name is: ent-01-vm-01.lab.eng.nay.redhat.com
[root@ent-01-vm-01 ~]# syspurpose show
{}
Unable to send system purpose to subscription management server
[root@ent-01-vm-01 ~]# 
[root@ent-01-vm-01 ~]# 
[root@ent-01-vm-01 ~]# subscription-manager service-level --set=Self-Support
[root@ent-01-vm-01 ~]# 
[root@ent-01-vm-01 ~]# 
[root@ent-01-vm-01 ~]# syspurpose show
{}
Unable to send system purpose to subscription management server
[root@ent-01-vm-01 ~]# 
[root@ent-01-vm-01 ~]# 
[root@ent-01-vm-01 ~]# subscription-manager service-level --set=test
[root@ent-01-vm-01 ~]# 
[root@ent-01-vm-01 ~]# syspurpose show
{}
Unable to send system purpose to subscription management server

Failed to verify this bug, please refer attachment 'rhsm.log'

Created attachment 1533928 [details]
rhsm.log

This appears to have been patched in subscription-manager-1.23.8-15.

Please retest with that version (or newer).

Verification on RHEL-8.0.0-20190228.1 against Satellite6.4.2:

subscription-manager-1.23.8-33.el8.x86_64
dnf-plugin-subscription-manager-1.23.8-33.el8.x86_64
subscription-manager-cockpit-1.23.8-33.el8.noarch
python3-subscription-manager-rhsm-1.23.8-33.el8.x86_64
subscription-manager-rhsm-certificates-1.23.8-33.el8.x86_64
tfm-rubygem-katello-3.7.0.46-1.el7sat.noarch
katello-3.7.0-8.el7sat.noarch
candlepin-2.4.8-1.el7.noarch

1. Register the system against Sat6.4:

[root@kvm-02-guest23 ~]# subscription-manager register
Registering to: ent-01-vm-01.lab.eng.nay.redhat.com:443/rhsm
Username: admin
Password: 
The system has been registered with ID: 74bfb27f-5181-48cf-9bd0-237a2000f4d5
The registered system name is: kvm-02-guest23.rhts.eng.bos.redhat.com

[root@kvm-02-guest23 ~]# syspurpose show <==== VERIFIED: Satellite6.4 does not support system purpose, so the output here is acceptable.
{}
Unable to send system purpose to subscription management server

[root@kvm-02-guest23 ~]# subscription-manager service-level --list
+-------------------------------------------+
               Available Service Levels
+-------------------------------------------+
Basic
Premium
Self-Support
Standard

2. Set a valid service level:

[root@kvm-02-guest23 ~]# subscription-manager service-level --set=Premium
Service level set to: "Premium".        <==== VERIFIED: setting a valid SLA successfully get an accurate notice.
[root@kvm-02-guest23 ~]# subscription-manager service-level --show
Current service level: Premium
[root@kvm-02-guest23 ~]# syspurpose show
{}
Unable to send system purpose to subscription management server


3. Set an invalid service level:
[root@kvm-02-guest23 ~]# subscription-manager service-level --set=test
Service level set to: "test".    <==== FAILED: the message shows invalid SLA is set successfully.
[root@kvm-02-guest23 ~]# echo $?
0
[root@kvm-02-guest23 ~]# subscription-manager service-level --show
Current service level: Premium   <==== FAILED: actually the invalid SLA is not set, and the setting keeps the same with step 2(a valid SLA)
[root@kvm-02-guest23 ~]# syspurpose show
{}
Unable to send system purpose to subscription management server


===================================
According to step 3, when setting an invalid service level, 'subscription-manager service-level --set' returns a inaccurate notice, because the invalid SLA is not set actually. So move the bug to NEW from ON_QA.

From a RHSM-QE perspective, comment 12 clearly shows that when a RHEL8 consumer registered to Satellite6.4 attempts to set a invalid SLA (due to an innocent typo), there is no feedback given and the value remains set to the former value.  This is indeed a usability regression where the original feedback expected was 'Service level "<INVALID-SLA>" is not available to units of organization <ORG-ID>.'

This change in usability was caused by the new "System Purpose" functionality on RHEL8 which is newly honoured when registered to a Satellite6.5 entitlement server that now permits consumers to set unavailable (including typos) service levels as part of their System Purpose attributes.  Hence we have a small backward (to Satellite6.4) regression in usability.

Note: Going forward on RHEL8 with Satellite6.5, RFE Bug 1632283 will be used to track the usability fix for this issue.

Since this is really a low severity (negative testing) issue against Satellite6.4, my vote would be to defer a fix (if possible - NEEDINFO from dev) to rhel-8.1.0 and add a rhel8.0 known-issue doc for this bug.

I agree with John in comment 13.

This is something that would be nice to have but not a blocker for 8.0.

Due to the low severity of this issue and the current phase of the satellite 6.4 (and lower) support lifecycle, we are closing this bug as wontfix.

Satellite 6.4 is currently in Maintenance Support Phase. This means only critical and security related bugs will be fixed.

https://access.redhat.com/support/policy/updates/satellite/

Please note this is only an issue against Satellite 6.4 and lower. It is not an issue against subscription.rhsm.redhat.com/subscription (Customer Portal).

The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days