Description of problem: Host's last report was 22 minutes ago, but it shows out of sync in the UI. irb(main):026:0> time_ago_in_words(host.last_report) => "25 minutes" irb(main):027:0> host.get_status(HostStatus::ConfigurationStatus) => #<HostStatus::ConfigurationStatus id: 9, type: "HostStatus::ConfigurationStatus", status: 117440512, host_id: 4, reported_at: "2016-03-24 04:21:21"> irb(main):028:0> host.get_status(HostStatus::ConfigurationStatus).to_label => "Out of sync" irb(main):029:0> Setting[:puppet_interval] => 30 Version-Release number of selected component (if applicable): 6.2 Snap 5.1 How reproducible: Always Steps to Reproduce: 1. Create a host managed by puppet Actual results: Some time after the first report shows up, the host will go to out of sync Expected results: Host shows OK up to Setting[:puppet_interval] after report Additional info:
Created redmine issue http://projects.theforeman.org/issues/14352 from this bug
Upstream bug component is Provisioning
Upstream bug component is Reporting
Based on the upstream comment on http://projects.theforeman.org/issues/14352 , I am updating the bugzilla to reference an issue that appears to already solve the behavior raised. That issue is http://projects.theforeman.org/issues/13883.
Verified with 2 hosts (using libvirt compute resource). Status was shown good after several reports. (see screenshots) Verified in Satellite 6.2-beta-snap-6
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/RHBA-2016:1501