Bug #855

some non-empty reports are not in interesting reports

Added by Yongchao Gao about 2 years ago. Updated 6 months ago.

Status:Closed Start:04/20/2011
Priority:Normal Due date:
Assigned to:Ohad Levy % Done:

0%
Category:-
Target version:1.1
Backlog:No Difficulity:
Votes: 0

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

201104210153.yaml (24.6 KB) Yongchao Gao, 04/20/2011 10:13 pm

History

Updated by Ohad Levy about 2 years ago

Any chance you could provide an example report?

it would greatly help to understand the issue.

Thanks

Updated by Ohad Levy about 2 years ago

also, if you can reproduce this error, does it happen on puppet newer than 2.6.5 ?

Updated by Yongchao Gao about 2 years ago

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 about 2 years ago

  • Assigned to 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 about 2 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 catalog

Any chance you could provide an example of such report too?

It is 201104210153.yaml not enough?

Updated by Ohad Levy about 2 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 catalog

Any 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 almost 2 years ago

  • Target version changed from 0.3 to 0.4

Updated by Ohad Levy over 1 year 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 6 months 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.

Also available in: Atom PDF