Bug #3171
closed
Foreman host reports are showing 0s (not showing skipped and others)
Added by Dmitry Kireev over 11 years ago.
Updated over 11 years ago.
Description
Upgraded foreman to 1.3 from 1.2
Upgraded puppet from 3.0 to 3.3
Downgraded from MariaDB to mysql 5.1x in order to have ability to use prebuild packages
Upgraded db driver to mysql2
Upgraded foreman.rb report and node.rb to newer versions.
Technically everything is working fine, and host status is OK, agent is not complaining about any reporting issues, but foreman host reports page is not able to show correct reprort information.
When you navigate to /hosts/hostname/reports all data is just zeros.
When you open one of the reports it is sometimes showing "nothing to show", sometimes actual run log, but it doesn't result in the previous page in any number of events (no skips or errors)
It seems to me as a bug, but I would love to prove that it is not.
Files
update, Errors and error states are showing up.
The state in the last two screenshots (old dashboard + reports page) are normal, as those only show "eventful" data - so reports with no applied, restarted, failed type counters won't show up.
I can't seem to reproduce the no logging data, nor can I see any issues with the "applied" counter. Have you done a full Apache restart since updating Puppet and/or the report processors?
My skipped column is always zero though, but I see some code that was ported from the 1.2 implementation into the 1.3 report processor that might have been designed to eliminate the "known" skips in the first place. I wonder if it's now working as designed. Greg? (https://github.com/theforeman/puppet-foreman/blob/master/templates/foreman-report_v2.rb.erb#L99)
- Status changed from New to Assigned
- Assignee set to Greg Sutcliffe
It's entirely possible, Dominic. I'll make a note to test in detail tomorrow and update the ticket.
- Status changed from Assigned to Need more information
My testing shows this to be a Puppet 3.3 thing. Foreman 1.3 with the v2 report processor still gets 6 skipped resources when I downgrade Puppet. I do note this in the PuppetDB 1.5 release notes:
- Filter out the well-known "Skipped Schedule" events: in versions of Puppet prior
to 3.3, every single agent report would include six events whose status was
`skipped` and whose resource type was `Schedule`. (The titles were `never`,
`puppet`, `hourly`, `daily`, `weekly`, and `monthly`.) These events were not
generally useful and caused a great deal of pollution in the PuppetDB database.
They are no longer generated as of Puppet 3.3, but for compatibility with
older versions of Puppet, the report terminus in PuppetDB 1.5 will filter
these events out before storing the report in PuppetDB.
I can't find which commit in 3.3 removed them, but I'm very happy to see them go :)
Dmitry, are there any other problems than the missing Skipped resources? If so, can you provide logs of a run with errors in, and the UI not showing those errors?
Greg, I think that is it. I don't see any issues with other things, and it actually is a good improvement.
Thanks everyone! Going back to enjoy my 1.3 and 3.3 !
- Status changed from Need more information to Resolved
- Target version deleted (
1.3.0)
Thanks for confirming Dmitry!
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by