You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Details of the scenario you tried and the problem that is occurring
In 8.5.0, powershellexecutionpolicy doesn't seem to work at all.
I found this, because in 8.4.0, there's an idempotency bug in which package when told to ensure something is Absent, will crash if it's absent. That may or may not be present in 8.5.0 as well, but my code didn't get that far in 8.5.0, I had to go back to 8.2.0.
Verbose logs showing the problem
For the package issue:
PowerShell DSC resource DSC_WindowsCapability failed to execute
Test-TargetResource functionality with error message: Specified Windows Capability
'OpenSSH.Server~~~~0.0.1.0' not found.
Sure, not found... but I'm asking it to, ya know, not be there, so we're good?
And ftr:
>Get-WindowsCapability-Online |where {$_.Name-like'*SSH*'}
Name : OpenSSH.Client~~~~0.0.1.0
State : NotPresent
Name : OpenSSH.Server~~~~0.0.1.0
State : NotPresent
Suggested solution to the issue
package should be idempotent
powershellexecutionpolicy should work
The DSC configuration that is used to reproduce the issue (as detailed as possible)
I'm using DSC primarily from Chef. I had originally thought this was a chef bug and filed one, but then I realized it was specific to ComputerManagementDsc 8.4.0 / 8.5.0 - going back to 8.2.0 solved the problem. Below is the relevant chef code, but feel free to give me things to run for testing and I will be happy to do so.
Details of the scenario you tried and the problem that is occurring
In 8.5.0,
powershellexecutionpolicy
doesn't seem to work at all.I found this, because in 8.4.0, there's an idempotency bug in which
package
when told to ensure something isAbsent
, will crash if it's absent. That may or may not be present in 8.5.0 as well, but my code didn't get that far in 8.5.0, I had to go back to 8.2.0.Verbose logs showing the problem
For the package issue:
Sure, not found... but I'm asking it to, ya know, not be there, so we're good?
And ftr:
Suggested solution to the issue
The DSC configuration that is used to reproduce the issue (as detailed as possible)
I'm using DSC primarily from Chef. I had originally thought this was a chef bug and filed one, but then I realized it was specific to ComputerManagementDsc 8.4.0 / 8.5.0 - going back to 8.2.0 solved the problem. Below is the relevant chef code, but feel free to give me things to run for testing and I will be happy to do so.
This fails in 8.5.0 for me
This fails in 8.4.0 and I expect fails in 8.5.0 but I can't test:
The operating system the target node is running
Version and build of PowerShell the target node is running
Version of the DSC module that was used ('dev' if using current dev branch)
8.4.0 / 8.5.0
The text was updated successfully, but these errors were encountered: