Jira (PUP-7036) Cannot configure a scheduled task with two "." in the name.

2016-12-20 Thread Patrick Magee (JIRA) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Patrick Magee updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-7036 
 
 
 
  Cannot configure a scheduled task with two "." in the name.   
 
 
 
 
 
 
 
 
 

Change By:
 
 Patrick Magee 
 
 
 
 
 
 
 
 
 
 *Environment*: Windows Server 2008 R2 Standard x64*Puppet Agent*: 3.7.2Example that does not work: `Prefix.ApplicationName.Suffix`.Example does work: `Prefix.ApplicationName_Suffix`.Both *do work if manually created* via the Task Scheduler GUI. There seems to be no name validation for tasks. Is this a bug of the Windows Task scheduler API that Ruby is using or something that Puppet should validate?We have a naming convention that applies to applications deployed where we use a Prefix for everything to identify a certain range of products and a Suffix for things such as Locale or Versions.*Works:*{code:java}scheduled_task { "${prefix}.${application}_${suffix}":ensure  => present,enabled => true,command => $command,arguments   => $arguments,working_dir => $working_directory,trigger => {  schedule   => daily,  every  => 1,  start_date => '2016-01-01',  start_time => $start_time}}{code}*Does not work:*{code:java}scheduled_task { "${prefix}.${application}.${suffix}":ensure  => present,enabled => true,command => $command,arguments   => $arguments,working_dir => $working_directory,trigger => {  schedule   => daily,  every  => 1,  start_date => '2016-01-01',  start_time => $start_time}}{code}Error output from Puppet Agent after running *puppet apply*:{noformat} {color:red} Error: Failed to call #::NewWorkItem with HRESULT: -2147024809.:  The parameter is incorrect.Error: /Stage[main]/Profiles::Application::Service/Scheduled_task[Prefix.Application.Suffix]/ensure: change from absent to present failed: Failed to call #::NewWorkItem with HRESULT: -2147024809.:  The parameter is incorrect. {color} {noformat}  
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)

Jira (PUP-7036) Cannot configure a scheduled task with two "." in the name.

2016-12-20 Thread Patrick Magee (JIRA) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Patrick Magee updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-7036 
 
 
 
  Cannot configure a scheduled task with two "." in the name.   
 
 
 
 
 
 
 
 
 

Change By:
 
 Patrick Magee 
 
 
 
 
 
 
 
 
 
 *Environment*: Windows Server 2008 R2 Standard x64*Puppet Agent*: 3.7.2Example that does not work: `Prefix.ApplicationName.Suffix`.Example does work: `Prefix.ApplicationName_Suffix`.Both *do work if manually created* via the Task Scheduler GUI. There seems to be no name validation for tasks. Is this a bug of the Windows Task scheduler API that Ruby is using or something that Puppet should validate?We have a naming convention that applies to applications deployed where we use a Prefix for everything to identify a certain range of products and a Suffix for things such as Locale or Versions.*Works:*{code:java}scheduled_task { "${prefix}.${application}_${suffix}":ensure  => present,enabled => true,command => $command,arguments   => $arguments,working_dir => $working_directory,trigger => {  schedule   => daily,  every  => 1,  start_date => '2016-01-01',  start_time => $start_time}}{code}*Does not work:*{code:java}scheduled_task { "${prefix}.${application}.${suffix}":ensure  => present,enabled => true,command => $command,arguments   => $arguments,working_dir => $working_directory,trigger => {  schedule   => daily,  every  => 1,  start_date => '2016-01-01',  start_time => $start_time}}{code}Error output from Puppet Agent after running *puppet apply*:{noformat} {color:red} Error: Failed to call #::NewWorkItem with HRESULT: -2147024809.:  The parameter is incorrect.Error: /Stage[main]/Profiles::Application::Service/Scheduled_task[Prefix.Application.Suffix]/ensure: change from absent to present failed: Failed to call #::NewWorkItem with HRESULT: -2147024809.:  The parameter is incorrect. {color} {noformat} 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)

Jira (PUP-7036) Cannot configure a scheduled task with two "." in the name.

2016-12-20 Thread Patrick Magee (JIRA) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Patrick Magee updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-7036 
 
 
 
  Cannot configure a scheduled task with two "." in the name.   
 
 
 
 
 
 
 
 
 

Change By:
 
 Patrick Magee 
 
 
 
 
 
 
 
 
 
 *Environment*: Windows Server 2008 R2 Standard x64*Puppet Agent*: 3.7.2Example that does not work: `Prefix.ApplicationName.Suffix`.Example does work: `Prefix.ApplicationName_Suffix`.Both *do work if manually created* via the Task Scheduler GUI. There seems to be no name validation for tasks. Is this a bug of the Windows Task scheduler API that Ruby is using or something that Puppet should validate?We have a naming convention that applies to applications deployed where we use a Prefix for everything to identify a certain range of products and a Suffix for things such as Locale or Versions.*Works:*{code:java}scheduled_task { "${prefix}.${application}_${suffix}":ensure  => present,enabled => true,command => $command,arguments   => $arguments,working_dir => $working_directory,trigger => {  schedule   => daily,  every  => 1,  start_date => '2016-01-01',  start_time => $start_time}}{code}*Does not work:*{code:java}scheduled_task { "${prefix}.${application}.${suffix}":ensure  => present,enabled => true,command => $command,arguments   => $arguments,working_dir => $working_directory,trigger => {  schedule   => daily,  every  => 1,  start_date => '2016-01-01',  start_time => $start_time}}{code} Error output from Puppet Agent after running *puppet apply*:{noformat}Error: Failed to call #::NewWorkItem with HRESULT: -2147024809.:  The parameter is incorrect.Error: /Stage[main]/Profiles::Application::Service/Scheduled_task[Prefix.Application.Suffix]/ensure: change from absent to present failed: Failed to call #::NewWorkItem with HRESULT: -2147024809.:  The parameter is incorrect.{noformat} 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe)

Jira (PUP-7036) Cannot configure a scheduled task with two "." in the name.

2016-12-20 Thread Patrick Magee (JIRA) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Patrick Magee updated an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-7036 
 
 
 
  Cannot configure a scheduled task with two "." in the name.   
 
 
 
 
 
 
 
 
 

Change By:
 
 Patrick Magee 
 
 
 
 
 
 
 
 
 
 *Environment*: Windows Server 2008 R2 Standard x64*Puppet Agent*: 3.7.2Example that does not work: `Prefix.ApplicationName.Suffix`.Example does work: `Prefix.ApplicationName_Suffix`.Both *do work if manually created* via the Task Scheduler GUI. There seems to be no name validation for tasks. Is this a bug of the Windows Task scheduler API that Ruby is using or something that Puppet should validate?We have a naming convention that applies to applications deployed where we use a Prefix for everything to identify a certain range of products and a Suffix for things such as Locale or Versions.*Works:*{code:java}scheduled_task { "${prefix}.${application}_${ locale suffix }":ensure  => present,enabled => true,command => $command,arguments   => $arguments,working_dir => $working_directory,trigger => {  schedule   => daily,  every  => 1,  start_date => '2016-01-01',  start_time => $start_time}}{code}*Does not work:*{code:java}scheduled_task { "${prefix}.${application}.${ locale suffix }":ensure  => present,enabled => true,command => $command,arguments   => $arguments,working_dir => $working_directory,trigger => {  schedule   => daily,  every  => 1,  start_date => '2016-01-01',  start_time => $start_time}}{code} 
 
 
 
 
 
 
 
 
 
 
 
 

 
 Add Comment 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 
 
 

 This message was sent by Atlassian JIRA (v6.4.14#64029-sha1:ae256fe) 
 
 
 
 
  
 
 
 
 
 
 
 
 
   





-- 
You

Jira (PUP-7036) Cannot configure a scheduled task with two "." in the name.

2016-12-20 Thread Patrick Magee (JIRA) 
Title: Message Title
 
 
 
 
 
 
 
 
 
 
  
 
 Patrick Magee created an issue 
 
 
 
 
 
 
 
 
 
 

 
 
 
 
 
 
 
 Puppet /  PUP-7036 
 
 
 
  Cannot configure a scheduled task with two "." in the name.   
 
 
 
 
 
 
 
 
 

Issue Type:
 
  Bug 
 
 
 

Assignee:
 

 Unassigned 
 
 
 

Created:
 

 2016/12/20 3:36 AM 
 
 
 

Labels:
 

 windows scheduled_task 
 
 
 

Priority:
 
  Normal 
 
 
 

Reporter:
 
 Patrick Magee 
 
 
 
 
 
 
 
 
 
 
Environment: Windows Server 2008 R2 Standard x64 Puppet Agent: 3.7.2 
Example that does not work: `Prefix.ApplicationName.Suffix`. Example does work: `Prefix.ApplicationName_Suffix`. 
Both do work if manually created via the Task Scheduler GUI. There seems to be no name validation for tasks. Is this a bug of the Windows Task scheduler API that Ruby is using or something that Puppet should validate? 
We have a naming convention that applies to applications deployed where we use a Prefix for everything to identify a certain range of products and a Suffix for things such as Locale or Versions. 
Works: 
 
 
 
 
 
 
scheduled_task { "${prefix}.${application}_${locale}":