1. Proposed title of this feature request

    [RFE] Remove InsightsReporting status affecting global host status from relvancy if insights disabled.

3. What is the nature and description of the request?

    As of Satellite 6.9.3, when building a host, a host status is set depending on whether that host has sent it's Insights report.
    If it has not, it reports as an error, and that error status then causes the entire host global status to be an error.
   
    If a user disables the Global Parameter 'host_insights_registration`, then all future hosts will have the Insights reporting status as "Ok" and will not cause the overall host to report an error, but perhaps no Insights Reporting status should be reported whatsoever if Insights reporting is disabled (either via disabling the global or overridden parameter for the host, or by disabling the Insights service entirely on the satellite).

4. Why does the customer need this? (List the business requirements here)

    If a customer doesn't use Insights, the Insights reporting status is irrelevant and should not affect the global status of the host one way or another.

5. How would the customer like to achieve this? (List the functional requirements here)

    If the Insights service is turned off by some mechanism (disabling the Global Parameter, or the parameter is overridden for a host maybe), then no status should be reported whatsoever.

6. For each functional requirement listed, specify how Red Hat and the customer can test to confirm the requirement is successfully implemented.

    Disable insights reporting.   Build a new host and "submit".  
    No Insights status should be set, as it is in either of the two screenshots in this article:   https://access.redhat.com/solutions/6176762

7. Is there already an existing RFE upstream or in Red Hat Bugzilla?

    No

8. Does the customer have any specific timeline dependencies and which release would they like to target (i.e. RHEL8, RHEL9)?

    No

9. Is the sales team involved in this request and do they have any additional input?

    No

10. List any affected packages or components.

   tfm-rubygem-foreman_rh_cloud-3.0.22-1.el7sat.noarch

11. Would the customer be able to assist in testing this functionality if implemented?

   Yes.