scheduled_task changes on every puppet run

[cko]

Hi,

I'm using the following scheduled_task on one of my windows server 2008 r2 boxes:

scheduled_task { 'reboot':
  command   => 'C:\WINDOWS\System32\shutdown.exe',
  arguments => "-r -f -t 01",
  user      => 'SYSTEM',
  trigger   => {
    schedule    => weekly,
    start_time  => '06:00',
    every       => 1,
    day_of_week => sun,
  }
}

Puppet creates the task and works just fine.

However, on every single puppet run the trigger changes (even though I didn't change the puppet code).

The report shows the following output:

 

Notice: /Stage[main]/Main/Node[NODE]/Scheduled_task[reboot]/trigger: trigger changed '{'every' => '1', 'on' => ['sun'], 'schedule' => 'weekly', 'start_date' => '2014-8-7', 'start_time' => '06:00'}' to '[{'day_of_week' => ['sun'], ' every' => '1', 'schedule' => 'weekly', 'start_time' => '06:00'}]' Notice: Finished catalog run in 6.55 seconds

 

Is there anything I can do to achieve idempotence with this scheduled task?

[Rob Reynolds]

This looks like you are running into PUP-1165[1]. Would you mind voting that issue up and commenting on it?

[1]: https://tickets.puppetlabs.com/browse/PUP-1165

 

--
You received this message because you are subscribed to the Google Groups "Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/29fafc9a-061f-442f-8efa-de7124c883f2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--

Rob Reynolds

Developer, Puppet Labs

Join us at PuppetConf 2014, September 20-24 in San Francisco

Register by September 8th to take advantage of the Final Countdown —save $149!

[aaronm]

I am getting similar logs every day, but I am not using any scheduled tasks in my manifests...

(**this is on PE 3.3 installed a week or two ago**)

trigger changed '{'every' => '1', 'schedule' => 'daily', 'start_date' => '2014-8-12', 'start_time' => '13:00'}' to '[{'every' => '1', 'schedule' => 'daily', 'start_time' => '13:00'}]'

/Stage[main]/Pe_mcollective::Server/Scheduled_task[pe-mcollective-metadata]/trigger

/opt/puppet/share/puppet/modules/pe_mcollective/manifests/server.pp

-------------------------------------------

(**this is from a longrunning PE server running 3.2 installed many months ago**)

trigger changed '{'every' => '1', 'schedule' => 'daily', 'start_date' => '2014-8-12', 'start_time' => '13:00'}' to '[{'every' => '1', 'schedule' => 'daily', 'start_time' => '13:00'}]'

/Stage[main]/Pe_mcollective::Server/Scheduled_task[pe-mcollective-metadata]/trigger

/opt/puppet/share/puppet/modules/pe_mcollective/manifests/server.pp

[Rob Reynolds]

On Wed, Aug 13, 2014 at 12:55 PM, aaronm <public...@gmail.com> wrote:

I am getting similar logs every day, but I am not using any scheduled tasks in my manifests...

(**this is on PE 3.3 installed a week or two ago**)

trigger changed '{'every' => '1', 'schedule' => 'daily', 'start_date' => '2014-8-12', 'start_time' => '13:00'}' to '[{'every' => '1', 'schedule' => 'daily', 'start_time' => '13:00'}]'

/Stage[main]/Pe_mcollective::Server/Scheduled_task[pe-mcollective-metadata]/trigger

/opt/puppet/share/puppet/modules/pe_mcollective/manifests/server.pp

-------------------------------------------

(**this is from a longrunning PE server running 3.2 installed many months ago**)

trigger changed '{'every' => '1', 'schedule' => 'daily', 'start_date' => '2014-8-12', 'start_time' => '13:00'}' to '[{'every' => '1', 'schedule' => 'daily', 'start_time' => '13:00'}]'

/Stage[main]/Pe_mcollective::Server/Scheduled_task[pe-mcollective-metadata]/trigger

/opt/puppet/share/puppet/modules/pe_mcollective/manifests/server.pp

The PE catalog includes a scheduled task. Would you mind following up on the pe-users group?

 

On Thursday, August 7, 2014 7:36:18 AM UTC-4, cko wrote:

Hi,

I'm using the following scheduled_task on one of my windows server 2008 r2 boxes:

scheduled_task { 'reboot':
  command   => 'C:\WINDOWS\System32\shutdown.exe',
  arguments => "-r -f -t 01",
  user      => 'SYSTEM',
  trigger   => {
    schedule    => weekly,
    start_time  => '06:00',
    every       => 1,
    day_of_week => sun,
  }
}

Puppet creates the task and works just fine.

However, on every single puppet run the trigger changes (even though I didn't change the puppet code).

The report shows the following output:

 

Notice: /Stage[main]/Main/Node[NODE]/Scheduled_task[reboot]/trigger: trigger changed '{'every' => '1', 'on' => ['sun'], 'schedule' => 'weekly', 'start_date' => '2014-8-7', 'start_time' => '06:00'}' to '[{'day_of_week' => ['sun'], ' every' => '1', 'schedule' => 'weekly', 'start_time' => '06:00'}]' Notice: Finished catalog run in 6.55 seconds

 

Is there anything I can do to achieve idempotence with this scheduled task?

--

You received this message because you are subscribed to the Google Groups "Puppet Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/puppet-users/e7823a79-676c-4c6e-a985-378d264e91f0%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.