** Note that this is a public ticket, please refrain from adding any sensitive data. **

User complaint:

We got the below advisor which recommends to set RHEL release to 8.8 from existing 8.10 as RHEL 8.8 is running on the host
Below is the details from the advisor

1st Advisor
The RHEL kernel can be accidentally upgraded to an uncertified release when it's not locked correctly for SAP HANA
The kernel version is not locked correctly for the running SAP HANA. This can result in accidentally upgrading to a kernel release which is not yet certified by SAP HANA.
Detected issues
RHEL 8.8 is running on this host; however, the Subscription Manager has set the RHEL release to 8.10 which puts the system at risk of accidentally upgrading to a kernel release which is not yet certified.
Steps to resolve
Red Hat recommends that you perform the following steps to set the RHEL kernel release to 8.8:
Set the kernel release

1. subscription-manager release --set=8.8
   Remove all cached data
2. yum clean all
   If you make sure the current release set 8.10 is correct, please perform the following steps to upgrade your kernel:
   Remove all cached data
3. yum clean all
   Upgrade the kernel
4. yum update kernel
   Note: Please make sure the upgraded kernel is certified by SAP HANA:
   SAP HANA: Supported Operating Systems .
   SAP HANA DB: Recommended OS settings for RHEL 8
   After applying the remediation, refresh the results of Advisor analysis by running the insights-client command on the system.
5. insights-client

We performed this and the alert cleared, but now a new alert/advisor has appeared which contradicts the previous advisor

2nd advisor
New advisor asks to set the RHEL release to 8.10
Decreased security: Unsupported RHEL release
Detected issues
This host is running RHEL 8 locked to the unsupported release 8.8.
As a result, important security updates are not available to this system.
yum update might not resolve issues indicated by other Insights recommendations.
Steps to resolve
Red Hat recommends that you use a supported RHEL release by unsetting the release lock.

1. subscription-manager release --unset
   Alternatively, if unsetting the release lock is not an option, fix this issue by re-setting the release lock to the latest RHEL release:
   List available releases.
2. subscription-manager release --list
   Set lock to the latest release, e.g. 8.10.
3. subscription-manager release --set=8.10
   Red Hat recommends that you test the change and review the new settings before applying them to production systems.
   After applying the remediation, refresh the results of Advisor analysis by running the insights-client command on the system.
4. insights-client

If we set RHEL to 8.10, 1st alert comes and if we set RHEl to 8.8 then 2nd alert shows up.

I am for now, just focusing on the first one which is most probably relevant to https://gitlab.cee.redhat.com/insights-rules/insights-plugins/-/blob/master/telemetry/rules/plugins/sap/sap_hana_rhsm_lock_issue.py?ref_type=heads . 

The system of the user seems to be a SAP HANA system ( but please check the sosreport ). 

And here in https://docs.redhat.com/en/documentation/red_hat_enterprise_linux_for_sap_solutions/8/html-single/rhel_for_sap_subscriptions_and_repositories/conscious-language-message_rhel-for-sap-subscriptions-and-repositories-8#con_hana_rhel-for-sap-subscriptions-and-repositories-8 or just the next section 3.3 , It seems SAP HANA is supported not only on 8.8 but also on 8.10 . 

It's only a matter of selecting and using the right repos for each. 

If we think that, The first rule is correct to say, set the release on 8.8, then the "Unsupported RHEL release" recommendation should be updated to exclude checking SAP\SAP-HANA systems or else users would be very confused.