Jira (PUP-1165) Spurious 'trigger changed' messages generated by scheduled task provider

2015-07-23 Thread C Lang (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 C Lang commented on  PUP-1165 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: Spurious 'trigger changed' messages generated by scheduled task provider  
 
 
 
 
 
 
 
 
 
 
Beyond documentation, shouldn't day_of_week either work or be removed? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-1165) Spurious 'trigger changed' messages generated by scheduled task provider

2015-07-23 Thread Rob Reynolds (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Rob Reynolds commented on  PUP-1165 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: Spurious 'trigger changed' messages generated by scheduled task provider  
 
 
 
 
 
 
 
 
 
 
I agree - should we file a documentation ticket Michelle Fredette? 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.5#64020-sha1:78acd6c) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-1165) Spurious 'trigger changed' messages generated by scheduled task provider

2015-05-22 Thread C Lang (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 C Lang commented on  PUP-1165 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: Spurious 'trigger changed' messages generated by scheduled task provider  
 
 
 
 
 
 
 
 
 
 
In 3.7.5, on a weekly task that was doing this to me, I found I could fix it simply by changing 'day_of_week' to 'on' - despite what the documentation says.  
Before that I was getting: 
trigger changed  
'[ {'enabled' = 'true', 'every' = '1', 'index' = '0', 'on' = ['mon'], 'schedule' = 'weekly', 'start_date' = '2015-5-22', 'start_time' = '03:00'} 
]' 
to 
'[ {'day_of_week' = 'mon', 'every' = '1', 'schedule' = 'weekly', 'start_date' = '2015-5-22', 'start_time' = '3:00'} 
]' 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-1165) Spurious 'trigger changed' messages generated by scheduled task provider

2015-05-22 Thread Rob Reynolds (JIRA)
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Rob Reynolds commented on  PUP-1165 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
  Re: Spurious 'trigger changed' messages generated by scheduled task provider  
 
 
 
 
 
 
 
 
 
 
Perhaps we need to update the documentation - it may already be updated.  
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 


 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.3.15#6346-sha1:dbc023d) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-1165) Spurious 'trigger changed' messages generated by scheduled task provider

2014-10-13 Thread Eric Thompson (JIRA)
Title: Message Title










 

 Eric Thompson commented on an issue


















  Re: Spurious 'trigger changed' messages generated by scheduled task provider 










verified in win2012r2-ruby64 at stable SHA a327be7 with






# use Josh's manifest as above




# change start_time




# run again:




Notice: Compiled catalog for bw72vphos85hyye.delivery.puppetlabs.net in environment production in 0.14 seconds




Notice: /Stage[main]/Main/Scheduled_task[spurious_task]/trigger: trigger changed '[{'enabled' = 'true', 'every' = '1', 'index' = '0', 'schedule' = 'daily', 'start_date' = '2014-10-13', 'start_time' = '15:00'}]' to '[{'every' = '1', 'schedule' = 'daily', 'start_time' = '16:20'}]'




Notice: Finished catalog run in 0.03 seconds




# run again:




$ cmd.exe /c puppet apply manifest.pp




Notice: Compiled catalog for bw72vphos85hyye.delivery.puppetlabs.net in environment production in 0.14 seconds




Notice: 

Jira (PUP-1165) Spurious 'trigger changed' messages generated by scheduled task provider

2014-10-13 Thread Eric Thompson (JIRA)
Title: Message Title










 

 Eric Thompson updated an issue


















 Puppet /  PUP-1165



  Spurious 'trigger changed' messages generated by scheduled task provider 










Change By:

 Eric Thompson




QA Contact:

 NarmadhaPerumal EricThompson




QA Status:

 Reviewed












   

 Add Comment






















 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














-- 
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-1165) Spurious 'trigger changed' messages generated by scheduled task provider

2014-10-09 Thread Rob Reynolds (JIRA)
Title: Message Title










 

 Rob Reynolds commented on an issue


















  Re: Spurious 'trigger changed' messages generated by scheduled task provider 










Merged into stable at 522ac8.












   

 Add Comment

























 Puppet /  PUP-1165



  Spurious 'trigger changed' messages generated by scheduled task provider 







 The Windows scheduled task (scheduled_task) provider will generate spurious messages during Puppet runs which suggest that scheduled task resources are being reapplied during each run even when the task is present and its associated resource has not been modified. The messages in question look like the following:   {noformat}notice: /Stage[main]/Schedtas...















 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














-- 
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-1165) Spurious 'trigger changed' messages generated by scheduled task provider

2014-10-07 Thread Rob Reynolds (JIRA)
Title: Message Title










 

 Rob Reynolds commented on an issue


















  Re: Spurious 'trigger changed' messages generated by scheduled task provider 










Found an issue, but I haven't dug into it yet Josh Cooper. I commented on the PR












   

 Add Comment

























 Puppet /  PUP-1165



  Spurious 'trigger changed' messages generated by scheduled task provider 







 The Windows scheduled task (scheduled_task) provider will generate spurious messages during Puppet runs which suggest that scheduled task resources are being reapplied during each run even when the task is present and its associated resource has not been modified. The messages in question look like the following:   {noformat}notice: /Stage[main]/Schedtas...















 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














-- 
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-1165) Spurious 'trigger changed' messages generated by scheduled task provider

2014-10-07 Thread Josh Cooper (JIRA)
Title: Message Title










 

 Josh Cooper assigned an issue to Josh Cooper


















 Puppet /  PUP-1165



  Spurious 'trigger changed' messages generated by scheduled task provider 










Change By:

 Josh Cooper




Assignee:

 RobReynolds JoshCooper












   

 Add Comment






















 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














-- 
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-1165) Spurious 'trigger changed' messages generated by scheduled task provider

2014-10-07 Thread Josh Cooper (JIRA)
Title: Message Title










 

 Josh Cooper assigned an issue to Rob Reynolds


















 Puppet /  PUP-1165



  Spurious 'trigger changed' messages generated by scheduled task provider 










Change By:

 Josh Cooper




Assignee:

 RobReynolds












   

 Add Comment






















 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














-- 
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-1165) Spurious 'trigger changed' messages generated by scheduled task provider

2014-10-06 Thread Josh Cooper (JIRA)
Title: Message Title










 

 Josh Cooper updated an issue


















 Puppet /  PUP-1165



  Spurious 'trigger changed' messages generated by scheduled task provider 










Change By:

 Josh Cooper




Story Points:

 1












   

 Add Comment






















 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














-- 
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-1165) Spurious 'trigger changed' messages generated by scheduled task provider

2014-10-06 Thread Kylo Ginsberg (JIRA)
Title: Message Title










 

 Kylo Ginsberg updated an issue


















 Puppet /  PUP-1165



  Spurious 'trigger changed' messages generated by scheduled task provider 










Change By:

 Kylo Ginsberg




Sprint:

 Platform2014-10- 29 15












   

 Add Comment






















 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














-- 
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-1165) Spurious 'trigger changed' messages generated by scheduled task provider

2014-10-06 Thread Kylo Ginsberg (JIRA)
Title: Message Title










 

 Kylo Ginsberg updated an issue


















 Puppet /  PUP-1165



  Spurious 'trigger changed' messages generated by scheduled task provider 










Change By:

 Kylo Ginsberg




Sprint:

 Platform2014-10-29












   

 Add Comment






















 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














-- 
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-1165) Spurious 'trigger changed' messages generated by scheduled task provider

2014-10-06 Thread Kylo Ginsberg (JIRA)
Title: Message Title










 

 Kylo Ginsberg updated an issue


















 Puppet /  PUP-1165



  Spurious 'trigger changed' messages generated by scheduled task provider 










Change By:

 Kylo Ginsberg




Flagged:

 Impediment












   

 Add Comment






















 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














-- 
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-1165) Spurious 'trigger changed' messages generated by scheduled task provider

2014-10-06 Thread Rob Reynolds (JIRA)
Title: Message Title










 

 Rob Reynolds commented on an issue


















  Re: Spurious 'trigger changed' messages generated by scheduled task provider 










I have seen equality checking on things that were not part of our api. I don't have a specific example at the moment though. If I take this for merge, I will try to find those issues again.












   

 Add Comment

























 Puppet /  PUP-1165



  Spurious 'trigger changed' messages generated by scheduled task provider 







 The Windows scheduled task (scheduled_task) provider will generate spurious messages during Puppet runs which suggest that scheduled task resources are being reapplied during each run even when the task is present and its associated resource has not been modified. The messages in question look like the following:   {noformat}notice: /Stage[main]/Schedtas...















 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














-- 
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at 

Jira (PUP-1165) Spurious 'trigger changed' messages generated by scheduled task provider

2014-10-06 Thread Rob Reynolds (JIRA)
Title: Message Title










 

 Rob Reynolds assigned an issue to Rob Reynolds


















 Puppet /  PUP-1165



  Spurious 'trigger changed' messages generated by scheduled task provider 










Change By:

 Rob Reynolds




Assignee:

 RobReynolds












   

 Add Comment






















 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














-- 
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-1165) Spurious 'trigger changed' messages generated by scheduled task provider

2014-10-03 Thread Josh Cooper (JIRA)
Title: Message Title










 

 Josh Cooper commented on an issue


















  Re: Spurious 'trigger changed' messages generated by scheduled task provider 










There are different behaviors depending on whether you are running 3.7.x or an earlier version. To reproduce the problem:
On 3.6.2, create a scheduled task whose trigger start_date is in the past. This simulates what puppet would do if it had run in the past and didn't specify a start_date:






scheduled_task { 'spurious_task':




  ensure  = 'present',




  command = 'c:\windows\system32\notepad.exe',




  enabled = 'true',




  trigger = {'every' = '1', 'schedule' = 'daily', 'start_time' = '15:16', 'start_date' = '1999-01-01'},




  user= 'system',




  working_dir = 'c:\windows\system32',




}







Apply the manifest and it correctly creates the scheduled task:





 

Jira (PUP-1165) Spurious 'trigger changed' messages generated by scheduled task provider

2014-10-03 Thread Josh Cooper (JIRA)
Title: Message Title










 

 Josh Cooper updated an issue


















 Puppet /  PUP-1165



  Spurious 'trigger changed' messages generated by scheduled task provider 










Change By:

 Josh Cooper




Fix Version/s:

 PUPfuture




Fix Version/s:

 PUP3.7.2












   

 Add Comment






















 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














-- 
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-1165) Spurious 'trigger changed' messages generated by scheduled task provider

2014-10-02 Thread Josh Cooper (JIRA)
Title: Message Title










 

 Josh Cooper commented on an issue


















  Re: Spurious 'trigger changed' messages generated by scheduled task provider 










The problem is the current task's trigger has a start_date component, which the desired task's trigger does not, so puppet thinks the trigger is out of sync. The logic for comparing triggers needs to account for cases where the desired start_date is not specified, where the current start_date is in the past (the task was created awhile ago), or the start_date is in the future.












   

 Add Comment

























 Puppet /  PUP-1165



  Spurious 'trigger changed' messages generated by scheduled task provider 







 The Windows scheduled task (scheduled_task) provider will generate spurious messages during Puppet runs which suggest that scheduled task resources are being reapplied during each run even when the task is present and its associated resource has not been modified. The messages in question look like the following:   {noformat}notice: /Stage[main]/Schedtas...















 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














-- 
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop 

Jira (PUP-1165) Spurious 'trigger changed' messages generated by scheduled task provider

2014-08-18 Thread Rob Reynolds (JIRA)
Title: Message Title










 

 Rob Reynolds updated an issue


















 Puppet /  PUP-1165



  Spurious 'trigger changed' messages generated by scheduled task provider 










Change By:

 Rob Reynolds




Labels:

 customer pe_mcollective redminewindows












   

 Add Comment






















 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














-- 
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-1165) Spurious 'trigger changed' messages generated by scheduled task provider

2014-08-18 Thread Rob Reynolds (JIRA)
Title: Message Title










 

 Rob Reynolds updated an issue


















 Puppet /  PUP-1165



  Spurious 'trigger changed' messages generated by scheduled task provider 










Change By:

 Rob Reynolds




Component/s:

 PE












   

 Add Comment






















 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














-- 
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-1165) Spurious 'trigger changed' messages generated by scheduled task provider

2014-08-12 Thread cko (JIRA)
Title: Message Title










 

 cko commented on an issue


















  Re: Spurious 'trigger changed' messages generated by scheduled task provider 










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















   

 Add Comment

























 Puppet /  PUP-1165



  Spurious 'trigger changed' messages generated by scheduled task provider 







 The Windows scheduled task (scheduled_task) provider will generate spurious messages during Puppet runs which suggest that scheduled task resources are being reapplied during each run even when the task is present and its associated resource has not been modified. The messages in question 

Jira (PUP-1165) Spurious 'trigger changed' messages generated by scheduled task provider

2014-08-11 Thread Rob Reynolds (JIRA)
Title: Message Title










 

 Rob Reynolds commented on an issue


















  Re: Spurious 'trigger changed' messages generated by scheduled task provider 










It appears the day_of_week versus on and start_date are what might be triggering this.












   

 Add Comment

























 Puppet /  PUP-1165



  Spurious 'trigger changed' messages generated by scheduled task provider 







 The Windows scheduled task (scheduled_task) provider will generate spurious messages during Puppet runs which suggest that scheduled task resources are being reapplied during each run even when the task is present and its associated resource has not been modified. The messages in question look like the following:   {noformat}notice: /Stage[main]/Schedtas...















 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














-- 
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-1165) Spurious 'trigger changed' messages generated by scheduled task provider

2014-08-11 Thread Rob Reynolds (JIRA)
Title: Message Title










 

 Rob Reynolds updated an issue


















 Puppet /  PUP-1165



  Spurious 'trigger changed' messages generated by scheduled task provider 










Change By:

 Rob Reynolds




Component/s:

 Client












   

 Add Comment






















 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














-- 
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-1165) Spurious 'trigger changed' messages generated by scheduled task provider

2014-08-11 Thread Rob Reynolds (JIRA)
Title: Message Title










 

 Rob Reynolds updated an issue


















 Puppet /  PUP-1165



  Spurious 'trigger changed' messages generated by scheduled task provider 










Change By:

 Rob Reynolds









 TheWindowsscheduledtask (scheduled_task) providerwillgeneratespuriousmessagesduringPuppetrunswhichsuggestthatscheduledtaskresourcesarebeingreappliedduringeachrunevenwhenthetaskispresentanditsassociatedresourcehasnotbeenmodified.Themessagesinquestionlooklikethefollowing:{noformat}notice:/Stage[main]/Schedtask/Scheduled_task[restart_some_service]/trigger:triggerchanged'{'every'='1','on'=['sun'],'schedule'='weekly','start_date'='2012-10-22','start_time'='01:00'}'to'[{'day_of_week'=['sun'],'schedule'='weekly','start_time'='01:00'}]'{noformat}Theresourceassociatedwiththetasklookslikethis:{noformat}scheduled_task{'restart_some_service':ensure=present,enabled=true,command='c:\windows\restart_some_service.bat',user='SYSTEM',trigger={schedule=weekly,day_of_week=[sun],start_time='01:00',},require=File['restart_some_service.bat'],}{noformat}Thisseemstobesomekindofartifactofdateconversion/formattingorsomething.WhilePuppetreportsachange,examiningthehistorytabforthetaskshowsnochangesasidefromtheinitialcreationofthetaskandsubsequent'real'changeswhichwereinitiatedbyactuallymodifyingtheresource.Thenoticeswillbegeneratedregardlessofwhetherthereisarealchangetoreport.












   

 Add Comment






















 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














-- 
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit 

Jira (PUP-1165) Spurious 'trigger changed' messages generated by scheduled task provider

2014-06-10 Thread Josh Cooper (JIRA)
Title: Message Title










 

 Josh Cooper updated an issue


















 Puppet /  PUP-1165



  Spurious 'trigger changed' messages generated by scheduled task provider 










Change By:

 Josh Cooper




Fix Version/s:

 future












   

 Add Comment






















 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














-- 
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-1165) Spurious 'trigger changed' messages generated by scheduled task provider

2014-06-04 Thread Josh Cooper (JIRA)
Title: Message Title










 

 Josh Cooper updated an issue


















 Puppet /  PUP-1165



  Spurious 'trigger changed' messages generated by scheduled task provider 










Change By:

 Josh Cooper




Component/s:

 TypesandProviders












   

 Add Comment






















 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














-- 
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/d/optout.


Jira (PUP-1165) Spurious 'trigger changed' messages generated by scheduled task provider

2014-06-04 Thread Josh Cooper (JIRA)
Title: Message Title










 

 Josh Cooper updated an issue


















 Puppet /  PUP-1165



  Spurious 'trigger changed' messages generated by scheduled task provider 










Change By:

 Josh Cooper









 TheWindowsscheduledtaskproviderwillgeneratespuriousmessagesduringPuppetrunswhichsuggestthatscheduledtaskresourcesarebeingreappliedduringeachrunevenwhenthetaskispresentanditsassociatedresourcehasnotbeenmodified.Themessagesinquestionlooklikethefollowing: code {noformat} notice:/Stage[main]/Schedtask/Scheduled_task[restart_some_service]/trigger:triggerchanged'{'every'='1','on'=['sun'],'schedule'='weekly','start_date'='2012-10-22','start_time'='01:00'}'to'[{'day_of_week'=['sun'],'schedule'='weekly','start_time'='01:00'}]' /code {noformat} Theresourceassociatedwiththetasklookslikethis: pre {noformat} scheduled_task{'restart_some_service':ensure=present,enabled=true,command='c:\windows\restart_some_service.bat',user='SYSTEM',trigger={schedule=weekly,day_of_week=[sun],start_time='01:00',},require=File['restart_some_service.bat'],} /pre {noformat} Thisseemstobesomekindofartifactofdateconversion/formattingorsomething.WhilePuppetreportsachange,examiningthehistorytabforthetaskshowsnochangesasidefromtheinitialcreationofthetaskandsubsequent'real'changeswhichwereinitiatedbyactuallymodifyingtheresource.Thenoticeswillbegeneratedregardlessofwhetherthereisarealchangetoreport.












   

 Add Comment






















 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














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

Jira (PUP-1165) Spurious 'trigger changed' messages generated by scheduled task provider

2013-12-30 Thread Joshua Cooper (JIRA)
Title: Message Title










 

 Joshua Cooper updated an issue


















 Puppet /  PUP-1165



  Spurious 'trigger changed' messages generated by scheduled task provider 










Change By:

 Joshua Cooper




Labels:

 customerredmine windows












   

 Add Comment






















 This message was sent by Atlassian JIRA (v6.1.4#6159-sha1:44eaede)




 














-- 
You received this message because you are subscribed to the Google Groups Puppet Bugs group.
To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com.
To post to this group, send email to puppet-bugs@googlegroups.com.
Visit this group at http://groups.google.com/group/puppet-bugs.
For more options, visit https://groups.google.com/groups/opt_out.


Jira (PUP-1165) Spurious 'trigger changed' messages generated by scheduled task provider

2013-12-18 Thread redmine.exporter (JIRA)
Title: Message Title










 

 redmine.exporter created an issue


















 Puppet /  PUP-1165



  Spurious 'trigger changed' messages generated by scheduled task provider 










Issue Type:

  Bug




Assignee:


 Unassigned




Created:


 18/Dec/13 4:52 AM




Labels:


 redmine customer




Priority:

  Normal




Reporter:

 redmine.exporter










The Windows scheduled task provider will generate spurious messages during Puppet runs which suggest that scheduled task resources are being reapplied during each run even when the task is present and its associated resource has not been modified. The messages in question look like the following:
codenotice: /Stage[main]/Schedtask/Scheduled_task[restart_some_service]/trigger: trigger changed ' {'every' = '1', 'on' = ['sun'], 'schedule' = 'weekly', 'start_date' = '2012-10-22', 'start_time' = '01:00'}
' to '[ {'day_of_week' = ['sun'], 'schedule' = 'weekly', 'start_time' = '01:00'}
]'/code
The resource associated with the task looks like this:
pre scheduled_task { 'restart_some_service': ensure = present, enabled = true, command = 'c:\windows\restart_some_service.bat', user = 'SYSTEM', trigger =  { schedule = weekly, day_of_week = [sun], start_time = '01:00', }
, require = File['restart_some_service.bat'], } /pre
This seems to be some kind of artifact of date conversion/formatting or something. While Puppet reports a change, examining the history tab for the task shows no changes aside from the initial creation of the task and subsequent 'real' changes which were