False skipped in report on clients that were upgraded from puppet 2.6 to 2.7

Support
1

Hi,

I am running Foreman 1.0.2 and I recently upgraded my server to puppet 2.7
(from 2.6). I also upgraded a few clients from 2.6 to 2.7. Everything
went well except for the fact that in my Foreman daily report, the clients
that are now on 2.7 show 288 skipped every day. If I parse the logs for
skipped on the client, I get nothing and "grep puppet /var/log/messages |
grep -v 'Finished catalog run in'" returns nothing. The only hint that I
saw is that just after upgrading the server to 2.7, I got this message in
the logs: "Authentication based on IP address is deprecated; please use
certname-based rules instead".

Thanks,

Ugo

2

That message isn't related. The skipped resources are "schedule"
resources which are built into Puppet
(https://docs.puppetlabs.com/references/latest/type.html#schedule).

Puppet 3.4.0 has a "default_schedules" setting which you can set to
false to disable them being added and IIRC in Puppet 3.5 they no longer
show up as skipped.

··· On 01/08/14 12:50, Ugo Bellavance wrote: > Hi, > > I am running Foreman 1.0.2 and I recently upgraded my server to puppet > 2.7 (from 2.6). I also upgraded a few clients from 2.6 to 2.7. > Everything went well except for the fact that in my Foreman daily > report, the clients that are now on 2.7 show 288 skipped every day. If > I parse the logs for skipped on the client, I get nothing and "grep > puppet /var/log/messages | grep -v 'Finished catalog run in'" returns > nothing. The only hint that I saw is that just after upgrading the > server to 2.7, I got this message in the logs: "Authentication based on > IP address is deprecated; please use certname-based rules instead".

–
Dominic Cleal
Red Hat Engineering