Bug #2245
Updated by Dominic Cleal over 11 years ago
Running foreman 1.1.1+debian1 (from foreman apt repo) on Debian Squeeze and puppetmaster 2.7.18-2 (all packages retreived from standard apt repos unless noted otherwise) on Debian Wheezy. Shared MySQL database, storeconfigs active. Certain reports are not listed as "eventful", even though changes have taken place. It turns out these changes are categorized as "skipped" instead. Please see attached reports_eventful_missing.png for the reports overview not listing the reports in question, and attached reports_eventful_detail_misparsed.png for a detail view of such a report. (Yes, the former picture has been taken long after the report came in.) This occurs with hosts running puppet 2.6.2-5+squeeze6 on Debian Squeeze and with hosts running puppet 2.6.3-0ubuntu1~lucid1 (from mathiaz-puppet-backports-lucid) on Ubuntu 10.04. Reports from hosts running puppet 2.7.18-2 on Debian Wheezy are displayed as expected, ie. listed as "eventful" when changes have taken place. For comparison / reference, here some data from another setup: Running foreman 1.0.2+debian1 (from foreman apt repo, installing 1.1.1+debian1 on Debian Squeeze is pending) on Debian Wheezy and puppetmaster 2.7.18-2 (all packages retreived from standard apt repos unless noted otherwise) on Debian Wheezy. Shared MySQL database, storeconfigs active. The following OS / puppet combinations are displayed correctly as "eventful" on changes: Ubuntu 10.04 running 0.25.4-2ubuntu6.8. The following OS / puppet combinations are not displayed correctly as "eventful" on changes, and the changes aren't listed as "skipped" either: Ubuntu 10.10 running 2.6.1-0ubuntu2 RHEL5 running 2.6.6-3.el5 (Snapshot from EPEL) Debian Squeeze running 2.6.8-1~bpo60+1+lfnet2 (own backport) Debian Lenny (don't ask) and Debian Etch (really, don't) running 2.6.8-1~bpo60+1+lfnet2~bpo50+1 (own backport) Ubuntu 12.04 running 2.7.11-1ubuntu2.1 Debian Wheezy running 2.7.18-2 A sample report detail of the latter is attached as reports_eventful_detail_missing.png. From a casual glance this seems to stem from app/models/report.rb, but I don't know enough about the different report formats / metrics to create a patch myself. However, if I should provide any additional data from the affected systems (e.g. stored raw reports), please don't hesitate to ask.