Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem:
- Showing "out of sync"status of all machines Under Hosts -> All hosts page.

Version-Release number of selected component (if applicable):

Satellite-6.9
How reproducible:
Repeatedly 

Steps to Reproduce:
1. ansible_out_of_sync_disabled and puppet_out_of_sync_disabled are both already set to true:

~~~
$ grep out_of_sync foreman_settings_table|cut -c 1-74
  21 | ansible_out_of_sync_disabled                           | --- true  
 152 | puppet_out_of_sync_disabled                            | --- true  
~~~


2. "out of sync"status for host on the satellite server  -> Under Hosts -> All hosts page.

Actual results:

Not honoring set values for ansible_out_of_sync_disabled and puppet_out_of_sync_disabled  as true.


Expected results:

Should be consider set value and not show  "Out of Sync"

Additional info:

Do you see new hosts becoming out of sync after the setting is disabled or hosts are out of sync prior setting is switch to disabled? The setting does is not supposed to reset any previous host status. If you clear the status from the host after you disable the out of sync for ansible, it should not re-appear.

This has been fixed in Sat - 7.0 in BZ#1825761 for workaround in older versions, please see https://bugzilla.redhat.com/show_bug.cgi?id=1800870#c22

*** This bug has been marked as a duplicate of bug 1825761 ***