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

We've observed a discrepancy in insights-client status on systems affected by RHINENG-18269 [0].

• Initially, $(insights-client --status) reports: "This host is registered":

[root@host ~]# insights-client --status
HTTPSConnectionPool(host='satellite.example.com', port=443): Max retries exceeded with url: /redhat_access/r/insights/v1/static/release/insights-core.el9.egg (Caused by SSLError(SSLCertVerificationError(1, '[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: self-signed certificate in certificate chain (_ssl.c:1147)'))) The Insights API could not be reached. This host is registered.

• However, after following the resolution steps in [1], the insights-client correctly shows that the host is in fact not registered:

[root@host ~]# rm /var/lib/insights/newest.egg* -f
[root@host ~]# insights-client && insights-client --version
This machine has not yet been registered. Use --register to register this machine.

The host failed to report for a while and so it was deleted from the inventory due to staleness.

I'm opening this JIRA to explore whether anything can be done to improve the accuracy of the registration status in such cases.

[0]https://issues.redhat.com/browse/RHINENG-18269

[1]https://access.redhat.com/solutions/7122649