Closed jdgoins closed 7 years ago
Thanks for following up with the issue @jdgoins! I'm not able to replicate your error. I'm using the same AMI, instance size as well as TK and winrm versions. Hard to say what the difference might be and the fact that it works without elevated eliminates most other possible culprits like proxy interference.
It may help to RDP to the instance and see if you can find anything in the event logs that might prove helpful. Also check to see if you see a schedule task created called WinRM_elevated_shell
. If so, does it look like it was ever run? Look at the script file the task loads and see if the contents of that file look off.
Another thing to look at is whether the command that the task is running would cause a reboot. I just ask because depending on timing, that could be a problem.
Closed. Issue was on our end.
@mwrock I mentioned this to you at ChefConf today.
I'm having an issue with elevated mode when I use the ec2 kitchen driver. A connection establishes properly when running normally, but not when I add
elevated: true
to my kitchen.yml file. I receive a 500 error reporting a bad response. This is running as part of my Chef Workflow pipeline. The Chef version, resource, and output are below.