This is my foreman host:
OS: redhat
RELEASE: Red Hat Enterprise Linux Server release 6.5 (Santiago)
FOREMAN: 1.5.2
RUBY: ruby 1.8.7 (2011-06-30 patchlevel 352) [x86_64-linux]
PUPPET: 3.4.3
I got a PuppetCA, Puppet master and TFTP proxy running and have already
provisioned one host.
However, it seems like every 30 minutes, I get a report saying "6"
resources are skipped.
I have no idea why it says so, I haven't scheduled anything and from
reading older post here, I haven't found any satisfying answer.
Does anyone know how I can tackle this? Is it a bad configuration in my
Puppet (although it has been configured from foreman-installer, IIRC)?
I also tried to see if there was some hints in the logs, but nothing
significant.
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 05/08/14 08:18, boaz s wrote:
> Hi there,
>
> This is my foreman host:
> OS: redhat
> RELEASE: Red Hat Enterprise Linux Server release 6.5 (Santiago)
> FOREMAN: 1.5.2
> RUBY: ruby 1.8.7 (2011-06-30 patchlevel 352) [x86_64-linux]
> PUPPET: 3.4.3
>
> I got a PuppetCA, Puppet master and TFTP proxy running and have already
> provisioned one host.
> However, it seems like every 30 minutes, I get a report saying "6"
> resources are skipped.
>
> I have no idea why it says so, I haven't scheduled anything and from
> reading older post here, I haven't found any satisfying answer.
> Does anyone know how I can tackle this? Is it a bad configuration in my
> Puppet (although it has been configured from foreman-installer, IIRC)?
> I also tried to see if there was some hints in the logs, but nothing
> significant.
Unfortunately, that doesn't help too.
I have added default_schedules = false under [agent] in
/etc/puppet/puppet.conf on both foreman host and the provisioned host.
And yes, I have also done service puppet restart after updating the
puppet.conf
Am I missing something? :\
···
On Tuesday, August 5, 2014 10:25:57 AM UTC+3, Dominic Cleal wrote:
>
> On 05/08/14 08:18, boaz s wrote:
> > Hi there,
> >
> > This is my foreman host:
> > OS: redhat
> > RELEASE: Red Hat Enterprise Linux Server release 6.5 (Santiago)
> > FOREMAN: 1.5.2
> > RUBY: ruby 1.8.7 (2011-06-30 patchlevel 352) [x86_64-linux]
> > PUPPET: 3.4.3
> >
> > I got a PuppetCA, Puppet master and TFTP proxy running and have already
> > provisioned one host.
> > However, it seems like every 30 minutes, I get a report saying "6"
> > resources are skipped.
> >
> > I have no idea why it says so, I haven't scheduled anything and from
> > reading older post here, I haven't found any satisfying answer.
> > Does anyone know how I can tackle this? Is it a bad configuration in my
> > Puppet (although it has been configured from foreman-installer, IIRC)?
> > I also tried to see if there was some hints in the logs, but nothing
> > significant.
>
> 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.
>
> --
> Dominic Cleal
> Red Hat Engineering
>
I don't know, that sounds enough. Adding it to the agent section of the
provisioned host and restarting Puppet should do it. Try running Puppet
in debug mode (puppet agent -t --debug) and see if it prints "Not
creating default schedules: default_schedules is false".
Otherwise I suggest trying Puppet 3.5 or higher, as I think it was also
removed by a second change.
···
On 05/08/14 09:26, boaz s wrote:
> Hi Dominic,
>
> Unfortunately, that doesn't help too.
> I have added `default_schedules = false` under `[agent]` in
> /etc/puppet/puppet.conf on both foreman host and the provisioned host.
> And yes, I have also done `service puppet restart` after updating the
> puppet.conf
>
> Am I missing something? :\
I have executed puppet agent -t --debug and have gotten the "Not
creating" message.
However, on the provisioned host, default_schedules is ignored and that
has been what I've gotten
info: Caching catalog for aqua-vds10.qa.lab.tlv.redhat.com
debug: Creating default schedules
debug: Loaded state in 0.00 seconds
info: Applying configuration version '1407026404'
debug: /Schedule[daily]: Skipping device resources because running on a host
debug: /Schedule[monthly]: Skipping device resources because running on a
host
debug: /Schedule[hourly]: Skipping device resources because running on a
host
debug: /Schedule[never]: Skipping device resources because running on a host
debug: /Schedule[weekly]: Skipping device resources because running on a
host
debug: /Schedule[puppet]: Skipping device resources because running on a
host
debug: Finishing transaction 70269748385520
Awkward, isn't it?
My assumption is due to the Puppet version.
The Foreman host is running Puppet 3.4.x while the provisioned host has
version 2.7.x.
I will continue look into it and update if I discover something unusual.
Anyhow, it does look that upgrading to Puppet 3.5 will fix this.
BR.
···
On Tuesday, August 5, 2014 11:33:24 AM UTC+3, Dominic Cleal wrote:
>
> On 05/08/14 09:26, boaz s wrote:
> > Hi Dominic,
> >
> > Unfortunately, that doesn't help too.
> > I have added `default_schedules = false` under `[agent]` in
> > /etc/puppet/puppet.conf on both foreman host and the provisioned host.
> > And yes, I have also done `service puppet restart` after updating the
> > puppet.conf
> >
> > Am I missing something? :\
>
> I don't know, that sounds enough. Adding it to the agent section of the
> provisioned host and restarting Puppet should do it. Try running Puppet
> in debug mode (puppet agent -t --debug) and see if it prints "Not
> creating default schedules: default_schedules is false".
>
> Otherwise I suggest trying Puppet 3.5 or higher, as I think it was also
> removed by a second change.
>
> --
> Dominic Cleal
> Red Hat Engineering
>
Right, the setting was added in Puppet 3.4.0. There's nothing you can
do on 2.7.
···
--
Dominic Cleal
Red Hat Engineering
On 05/08/14 10:45, boaz s wrote:
You’re definitely right, chap!
I have executed puppet agent -t --debug and have gotten the “Not
creating” message.
However, on the provisioned host, default_schedules is ignored and
that has been what I’ve gotten
info: Caching catalog for aqua-vds10.qa.lab.tlv.redhat.com
debug: Creating default schedules
debug: Loaded state in 0.00 seconds
info: Applying configuration version ‘1407026404’
debug: /Schedule[daily]: Skipping device resources because running on a host
debug: /Schedule[monthly]: Skipping device resources because running on
a host
debug: /Schedule[hourly]: Skipping device resources because running on a
host
debug: /Schedule[never]: Skipping device resources because running on a host
debug: /Schedule[weekly]: Skipping device resources because running on a
host
debug: /Schedule[puppet]: Skipping device resources because running on a
host
debug: Finishing transaction 70269748385520
Awkward, isn’t it?
My assumption is due to the Puppet version.
The Foreman host is running Puppet 3.4.x while the provisioned host has
version 2.7.x.
I will continue look into it and update if I discover something unusual.
Anyhow, it does look that upgrading to Puppet 3.5 will fix this.
BR.
On Tuesday, August 5, 2014 11:33:24 AM UTC+3, Dominic Cleal wrote:
On 05/08/14 09:26, boaz s wrote:
> Hi Dominic,
>
> Unfortunately, that doesn't help too.
> I have added `default_schedules = false` under `[agent]` in
> /etc/puppet/puppet.conf on both foreman host and the provisioned
host.
> And yes, I have also done `service puppet restart` after updating the
> puppet.conf
>
> Am I missing something? :\
I don't know, that sounds enough. Adding it to the agent section of
the
provisioned host and restarting Puppet should do it. Try running
Puppet
in debug mode (puppet agent -t --debug) and see if it prints "Not
creating default schedules: default_schedules is false".
Otherwise I suggest trying Puppet 3.5 or higher, as I think it was also
removed by a second change.
--
Dominic Cleal
Red Hat Engineering
