Bug #855
closed
some non-empty reports are not in interesting reports
Description
Some reports are not displayed at the intersting reports, such as :
notice /Stage[main]/Puppet/Cron::Add[cron for foreman]/File[/etc/cron.d/puppet]/content content changed '{md5}e440d42c80b638143d86f12ff75be789' to '{md5}d2890be63b02afc9c854e803e828bb87'
And the applied number of this report is also zero.
My puppet is 2.6.2, and foreman is 0.2.0
Files
| 201104210153.yaml | 201104210153.yaml | 24.6 KB | |||
| Screen Shot 2014-09-14 at 3.13.32 PM.png | View Screen Shot 2014-09-14 at 3.13.32 PM.png | 140 KB | host's report |
Updated by Ohad Levy almost 14 years ago
Any chance you could provide an example report?
it would greatly help to understand the issue.
Thanks
Updated by Ohad Levy almost 14 years ago
also, if you can reproduce this error, does it happen on puppet newer than 2.6.5 ?
Updated by Yongchao Gao almost 14 years ago
- File 201104210153.yaml 201104210153.yaml added
Thanks for your reply, after upgrading puppet to 2.6.7, this error seems to be disappear.
But i found another problem that the error report is not in interesting reports, the report such as :
err Puppet Could not retrieve catalog from remote server: Error 400 on SERVER: Could not find template 'rabbitmq/logrotate/rabbitmq-server.erb' at /home/flex/puppet/modules/logrotate/manifests/init.pp:12 on node dori.test.com
notice Puppet Using cached catalog
Updated by Ohad Levy almost 14 years ago
- Assignee set to Ohad Levy
- Target version set to 0.3
Yongchao Gao wrote:
Thanks for your reply, after upgrading puppet to 2.6.7, this error seems to be disappear.
But i found another problem that the error report is not in interesting reports, the report such as :
err Puppet Could not retrieve catalog from remote server: Error 400 on SERVER: Could not find template 'rabbitmq/logrotate/rabbitmq-server.erb' at /home/flex/puppet/modules/logrotate/manifests/init.pp:12 on node dori.test.com
notice Puppet Using cached catalog
Any chance you could provide an example of such report too?
Updated by Yongchao Gao almost 14 years ago
Ohad Levy wrote:
Yongchao Gao wrote:
Thanks for your reply, after upgrading puppet to 2.6.7, this error seems to be disappear.
But i found another problem that the error report is not in interesting reports, the report such as :
err Puppet Could not retrieve catalog from remote server: Error 400 on SERVER: Could not find template 'rabbitmq/logrotate/rabbitmq-server.erb' at /home/flex/puppet/modules/logrotate/manifests/init.pp:12 on node dori.test.com
notice Puppet Using cached catalogAny chance you could provide an example of such report too?
It is 201104210153.yaml not enough?
Updated by Ohad Levy almost 14 years ago
Yongchao Gao wrote:
Ohad Levy wrote:
Yongchao Gao wrote:
Thanks for your reply, after upgrading puppet to 2.6.7, this error seems to be disappear.
But i found another problem that the error report is not in interesting reports, the report such as :
err Puppet Could not retrieve catalog from remote server: Error 400 on SERVER: Could not find template 'rabbitmq/logrotate/rabbitmq-server.erb' at /home/flex/puppet/modules/logrotate/manifests/init.pp:12 on node dori.test.com
notice Puppet Using cached catalogAny chance you could provide an example of such report too?
It is 201104210153.yaml not enough?
yep, sorry, i thought the report you sent was for the first issue..
Updated by Ohad Levy over 13 years ago
- Target version deleted (
0.4)
i cant reproduce the problem with the latest foreman version, if this happens again please, upload a broken report file
Updated by Benjamin Papillon about 12 years ago
- Status changed from New to Closed
- Target version set to Bug scrub
Hello,
Due to lack of update we are closing this bug.
Please, reopen it if you still have the problem with newer builds.
Updated by Trey Dockendorf over 10 years ago
Running Foreman 1.5.0 I just ran into this.
A host's reports show as "no changes" when the actual report contains the following:
Could not apply complete catalog: Found 1 dependency cycle: (Anchor[zabbix::agent::end] => Class[Zabbix::Agent] => Zabbix::Agent::Userparameter[mdraid] => File[userparameter_mdraid.conf] => Service[zabbix-agent] => Class[Zabbix::Agent::Service] => Anchor[zabbix::agent::end]) Try the '--graph' option and opening the resulting '.dot' file in OmniGraffle or GraphViz
Attached is screenshot showing the report in GUI. This particular error happened across ALL my servers (oops :-X) but the GUI shows all systems as having good reports.
Updated by Anonymous over 10 years ago
- Description updated (diff)
- Category set to Puppet Reports
- Status changed from Closed to Assigned
- Assignee changed from Ohad Levy to Trey Dockendorf
- Target version deleted (
1.1)
as requested in IRC
Updated by Anonymous over 10 years ago
- Is duplicate of Bug #3851: Reports with errors on the puppet master side are not shown as failed added
Updated by Trey Dockendorf over 10 years ago
- Status changed from Assigned to Closed
Disregard my last comment. I was using theforeman/foreman module v2.1.3 and this issue was fixed in v2.1.4. Updating the puppet module resolved the issue.