Jira (PUP-9074) Windows scheduled_task name cannot us a path

8 views
Skip to first unread message

Peter J Krawetzky (JIRA)

unread,
Aug 17, 2018, 10:10:04 AM8/17/18
to puppe...@googlegroups.com
Peter J Krawetzky created an issue
 
Puppet / Bug PUP-9074
Windows scheduled_task name cannot us a path
Issue Type: Bug Bug
Affects Versions: PUP 4.10.4
Assignee: Unassigned
Components: Windows
Created: 2018/08/17 7:09 AM
Priority: Normal Normal
Reporter: Peter J Krawetzky

Puppet Version:  4.10.4
Puppet Server Version:  5.3.4
OS Name/Version:  Windows 2016 10.0.14393

When trying to execute the follow resource on a Windows 2016 server an error is returned:

scheduled_task { '\Puppet\PuppetKickoff':
  ensure    => present,
  enabled   => true,
  command   => 'powershell.exe',
  arguments => ' E:
Program Files\\PuppetLabs\\bin
run_puppet_shell.bat -Verb runas',
  trigger   => {
    schedule   => daily,
    every      => 1,            # Specifies every other day. Defaults to 1 (every day).
    start_time => '08:${puppet_agent::params::cronminute}',      # Must be specified
    minutes_interval => '60',   # Repeat this task every 60 minutes
    minutes_duration => '300',  # The task will run for a total of five hours
  }

 

Error:

Error: Failed to call #<Win32::TaskScheduler::COM::TaskScheduler:0x0000000926cd08>::NewWorkItem with HRESULT: -2147024893.:  The system cannot find the path specified.

Error: /Stage[main]/Puppet_agent::Init_windows/Scheduled_task[\Puppet\PuppetKickoff]/ensure: change from absent to present failed: Failed to call #<Win32::TaskScheduler::COM::TaskScheduler:0x0000000926cd08>::NewWorkItem with HRESULT: -2147024893.:  The system cannot find the path specified.

When I only use PuppetKickoff in the name, it sucessfully creates a scheduled task but not in the path I desire.

Desired Behavior:

Allow a path structure in the scheduled_task name in order to place a task away from the main path

Actual Behavior:

See above

Add Comment Add Comment
 
This message was sent by Atlassian JIRA (v7.7.1#77002-sha1:e75ca93)
Atlassian logo

Geoff Nichols (JIRA)

unread,
Aug 22, 2018, 12:46:05 PM8/22/18
to puppe...@googlegroups.com
Geoff Nichols updated an issue
 
Puppet / New Feature PUP-9074
Change By: Geoff Nichols
Issue Type: Bug New Feature

Geoff Nichols (JIRA)

unread,
Aug 22, 2018, 12:46:10 PM8/22/18
to puppe...@googlegroups.com

Geoff Nichols (JIRA)

unread,
Aug 22, 2018, 12:47:10 PM8/22/18
to puppe...@googlegroups.com
Geoff Nichols updated an issue
Change By: Geoff Nichols
Sprint: Windows Grooming

Erick Banks (JIRA)

unread,
Feb 7, 2019, 8:24:15 PM2/7/19
to puppe...@googlegroups.com
Erick Banks updated an issue
Change By: Erick Banks
Sprint: Windows Grooming

Peter J Krawetzky (JIRA)

unread,
Sep 3, 2019, 9:47:03 AM9/3/19
to puppe...@googlegroups.com
Peter J Krawetzky commented on New Feature PUP-9074
 
Re: Windows scheduled_task name cannot us a path

Any idea if this has been fixed?

Josh Cooper (Jira)

unread,
Mar 4, 2020, 10:30:04 AM3/4/20
to puppe...@googlegroups.com
Josh Cooper updated an issue
 
Change By: Josh Cooper
*Puppet Version:  4.10.4*
*Puppet Server Version:  5.3.4*
*OS Name/Version:  Windows 2016 10.0.14393*


When trying to execute the follow resource on a Windows 2016 server an error is returned:

{code:puppet}

scheduled_task { '\Puppet\PuppetKickoff':
  ensure    => present,
  enabled   => true,
  command   => 'powershell.exe',
  arguments => ' E:\\Program Files\\PuppetLabs\\bin\\run_puppet_shell.bat -Verb runas',
  trigger   => {
    schedule   => daily,
    every      => 1,            # Specifies every other day. Defaults to 1 (every day).
    start_time => '08:${puppet_agent::params::cronminute}',      # Must be specified
    minutes_interval => '60',   # Repeat this task every 60 minutes
    minutes_duration => '300',  # The task will run for a total of five hours
  }
}
{code}

Error:

{noformat}

Error: Failed to call #<Win32::TaskScheduler::COM::TaskScheduler:0x0000000926cd08>::NewWorkItem with HRESULT: -2147024893.:  The system cannot find the path specified.

Error: /Stage[main]/Puppet_agent::Init_windows/Scheduled_task[\Puppet\PuppetKickoff]/ensure: change from absent to present failed: Failed to call #<Win32::TaskScheduler::COM::TaskScheduler:0x0000000926cd08>::NewWorkItem with HRESULT: -2147024893.:  The system cannot find the path specified.
{noformat}


When I only use PuppetKickoff in the name, it sucessfully creates a scheduled task but not in the path I desire.



*Desired Behavior:*


Allow a path structure in the scheduled_task name in order to place a task away from the main path

*Actual Behavior:*

See above
This message was sent by Atlassian Jira (v8.5.2#805002-sha1:a66f935)
Atlassian logo

Josh Cooper (Jira)

unread,
Mar 4, 2020, 10:30:04 AM3/4/20
to puppe...@googlegroups.com
Reply all
Reply to author
Forward
0 new messages