-
Type:
Bug
-
Status: Resolved
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: None
-
Fix Version/s: PowerShell 2.1.3, DSC 1.4.1
-
Component/s: powershell
-
Labels:
-
Environment:
Windows: 2012, 2012r2, 2016
R320's, R620's, R720's. 64-256 GB of RAM
Powershell 5.0 and 4.0
-
Template:
-
Epic Link:
-
Team:Windows
-
Sprint:Windows Kanban
-
Zendesk Ticket IDs:41624
-
Zendesk Ticket Count:1
-
QA Risk Assessment:Needs Assessment
Basic Info
Module Version: 2.1.0
Puppet Version: 3.7.3
OS Name/Version: 2012, 2012r2, 2016
Powershell v4 and v5
Describe your issue in as much detail as possible...
Multiple issues across multiple modules and commands:
Could not evaluate: Failure waiting for PowerShell process <pid> to start pipe server
|
Pipes are working. We have .net 3.5 on these.
Desired Behavior:
Powershell executes commands without issue.
Actual Behavior:
Powershell commands fail. Appears to be totally random on what kind of command.
Unfortunately thats about it for the logs. A Powershell failure and thats it. Really hard to troubleshoot or capture anymore.
- relates to
-
MODULES-6296 DSC 1.4.1
-
- Closed
-
-
MODULES-8194 powershell : allow pipe_timeout to be configurable
-
- Accepted
-
-
MODULES-4754 PowerShell: Exit powershell_manager earlier in Puppet run
-
- Resolved
-