Closed gsperry2011 closed 2 years ago
If anyone comes across this, I stopped getting this issue by upgrading powershell to 5.1
Name Value
---- -----
PSVersion 5.1.14409.1005
PSEdition Desktop
PSCompatibleVersions {1.0, 2.0, 3.0, 4.0...}
BuildVersion 10.0.14409.1005
CLRVersion 4.0.30319.42000
WSManStackVersion 3.0
PSRemotingProtocolVersion 2.3
SerializationVersion 1.1.0.1
I want to start this issue out by saying I don't think there is an issue with this module. I've been using it for years and had not seen this issue before yesterday. I wanted to post it here to see if anyone else is having the same issue and I imagine anyone else having this same issue might look here for some info about it (I know I did).
Affected Puppet, Ruby, OS and module versions/distributions
latest
How to reproduce (e.g Puppet code you use) :
I believe implying using the
windowsfeature
provider will cause this error.What are you seeing:
I found this rather odd because the only error i'm seeing is that the exit code was a
1
. Sure enough when I try and run the same powershell command Puppet is, I also get an exit code of1
-- Powershell seems to be able to generate an XML with no issue though. In the picture below you can see that when I runC:\Windows\system32\WindowsPowershell\v1.0\powershell.exe Import-Module ServerManager; Get-WindowsFeature | Select-Object -Property Name, Installed | ConvertTo-XML -As String -Depth 4 -NoTypeInformation
I get an exit code of1
and to sanity check I run thehostname
command to check it's exit code and sure enough a0
should mean a success.What behaviour did you expect instead: No errors
Output log:
Any additional information you'd like to impart