The Puppet Labs Issue Tracker has Moved:

Bug #14071

Puppet::Util::execute semantics, on Windows, don't match POSIX or Puppet expectations.

Added by Anonymous almost 3 years ago. Updated about 1 year ago.

Status:AcceptedStart date:04/18/2012
Priority:NormalDue date:
Assignee:Josh Cooper% Done:


Target version:3.x
Affected Puppet version:2.7.6 Branch:
Keywords:windows exec

We've Moved!

Ticket tracking is now hosted in JIRA:

This ticket is now tracked at:


A whole bunch of code in Puppet expects that you can pass a white-space separated string to Puppet::Util::execute, in an array, and have it figure out the executable that should be run.

For example, in master, lib/puppet/resource/type_collection.rb:141 has this expectation – and on POSIX platforms, that is satisfied.

The semantics should probably match on different platforms. This is the last remaining point blocking external configuration version commands working on Windows, despite what that file says.

Related issues

Related to Puppet - Bug #15693: windows service provider restart method cannot be overridden Closed 07/25/2012
Related to Puppet - Bug #17603: Puppet execute has unexpected semantics Accepted
Related to Puppet - Bug #22490: CreateProcess() failed when specifying service restart co... Accepted


#1 Updated by Josh Cooper almost 3 years ago

  • Status changed from Needs Decision to Accepted
  • Affected Puppet version set to 2.7.6
  • Keywords set to windows exec

#2 Updated by Josh Cooper about 1 year ago

Redmine Issue #14071 has been migrated to JIRA:

Also available in: Atom PDF