Bug 2167389

Summary: Missing type and details for host_registration_insights parameter
Product: Red Hat Satellite Reporter: Shimon Shtein <sshtein>
Component: RH Cloud - InsightsAssignee: Malhar Jivrajani <mjivraja>
Status: CLOSED CURRENTRELEASE QA Contact: Satellite QE Team <sat-qe-bz-list>
Severity: medium Docs Contact: Malhar Jivrajani <mjivraja>
Priority: unspecified    
Version: 6.11.0CC: aruzicka, bbuckingham, egolov, mdolezel, mjivraja, peter.vreman
Target Milestone: UnspecifiedKeywords: Documentation, Triaged
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-05-29 17:25:19 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Shimon Shtein 2023-02-06 13:59:40 UTC
Description of problem:

The only mention of host_registration_insights parameter is in upstream:
https://docs.theforeman.org/nightly/Managing_Hosts/index-katello.html#Customizing_the_Registration_Templates_managing-hosts

We should add a mention that the parameter type is boolean.

While we are there, we should also mention that the same parameter also prevents hosts from appearing in rh_cloud reports if the parameter is set to false. Another usage of the parameter is to prevent insights-client from uploading its reports in case the parameter is set to false.

Comment 2 Peter Vreman 2023-02-06 19:10:42 UTC
The documentation in the registration templates section is not a correct place.  It is a generic host parameter settings that is always application for everybody that does not want that Sat6 is uploading hosts to c.r.c

Maybe the word parameter is even incorrect and it is a real host/hostgroup configuration that affects multiple (daily) workflows:
- daily sat6 inventory upload
- block insights-client connections

Maybe a real host/hostgroup record configuration setting instead of a template parameter is better applicable here