I'm still having a big problem trying to get schedule{} and the --
onetime command-line option to play nice together. This is on 0.24.8,
but also seem to have the issue with 0.25.4.
I have a custom schedule in my manifest:
schedule { development:
range => "05:00 - 23:59", repeat => 12, period => hourly,
}
Also, resource defaults that apply that schedule:
File { schedule => development }
Package { schedule => development }
Service { schedule => development }
Exec { schedule => development }
Cron { schedule => development }
Tidy { schedule => development }
Augeas { schedule => development }
Group { schedule => development }
User { schedule => development }
This runs fine with puppetd running as a daemon, and the resources are
applied as expected during the time periods allowed. However, when I
run "puppetd --onetime", none of the resources are applied, the run
time of the process is very short (a full run is about 45 seconds):
Aug 19 12:44:31 vm10 puppetd[23513]: Reopening log files
Aug 19 12:44:31 vm10 puppetd[23513]: Ignoring --listen on onetime run
Aug 19 12:45:04 vm10 puppetd[23513]: Starting catalog run
Aug 19 12:45:08 vm10 puppetd[23513]: Finished catalog run in 4.27
seconds
If, however, I invoke it as "puppetd --onetime --ignoreschedules" I'll
indeed get what is expected.
Is --onetime incompatible with having a schedule object? Or is there
some trick to it? I'm trying to integrate mcollective into our
environment, and I'd like to have the schedules work as a safety net
to not (by default) allow a run during production hours.
Thanks in advance for any tips or suggestions.
-Alan
--
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-us...@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
