Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
This means that every host that hasn't reported in the last 5 minutes is out of sync. With Puppet the default interval is 30 minutes which means that most of your infra is out of sync all the time.
commit:348ec9c0d6ff6c2574c5e6dddbe8e9203d73d2e8 introduced this setting.
To restore the original behavior, this should be CPed to 6.4.
Reproducing steps:
1) setup host with default puppet interval, make sure puppet run takes a while
2) wait for 30 minutes
3) host is marked as out of sync after 30 minutes, when puppet run finishes, e.g. 31th minute, it's green again
Actual results:
There used to be out of sync field that was a safety bumper, defaulting to 5 minutes. Its meaning has changed so to restore original behavior, puppet interval in settings should be set to 35
Expected results: puppet_interval setting is automatically set to 35 on new instance and is upgraded to 35 on upgrade, if 6.3 default value remained at 30. If user changed it e.g. to 60, then it remains 60.
Comment 5Satellite Program
2018-08-13 14:20:10 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHSA-2018:2927
Comment 11Red Hat Bugzilla
2023-09-14 04:33:04 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days