Bug 1615351
| Summary: | Default out of sync interval is 5 minutes | ||
|---|---|---|---|
| Product: | Red Hat Satellite | Reporter: | Marek Hulan <mhulan> |
| Component: | Reporting | Assignee: | Sebastian Gräßl <sgraessl> |
| Status: | CLOSED ERRATA | QA Contact: | Perry Gagne <pgagne> |
| Severity: | high | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 6.2.0 | CC: | inecas, mhulan, oprazak, sgraessl, zhunting |
| Target Milestone: | 6.4.0 | Keywords: | Triaged |
| Target Release: | Unused | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | foreman-1.18.0.10-1 | Doc Type: | If docs needed, set a value |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2018-10-16 19:28:11 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Marek Hulan
2018-08-13 12:03:31 UTC
Created from redmine issue https://projects.theforeman.org/issues/24350 Upstream bug assigned to sgraessl 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. Moving this bug to POST for triage into Satellite 6 since the upstream issue https://projects.theforeman.org/issues/24350 has been resolved. *** Bug 1615350 has been marked as a duplicate of this bug. *** 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 The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days |