VMware shutdown fails#4041
Conversation
Resolves issue where `shutdown_command` would error because the remote side disconnected, which we should have expected and ignored.
|
only thing I can think of this breaks is if there's a non-0 exit from command_shutdown and the vm stays up. With this it immediately crashes, but without it times out for I think we can get rid of this safely |
|
Closes #4054 |
|
Confirming this fixes the issue for me on latest Packer build. |
|
Had the regression and this is working for me now. |
|
This fix is good and I have tested it a few times. |
Port hashicorp#4041 to hyperv-iso builder
|
I seem to be running into this with packer 1.3.3 PS C:\windows\temp> packer --version ... |
|
@helperton this was merged two years ago, so I suspect that if you're seeing something it's new; can you open a new ticket with steps to reproduce? |
|
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further. |
WIP. should resolve issue reported in #4034
I looked at how all the other shutdown steps did this:
and saw none of them actually wait for the remote command to end gracefully.
vmware's step shut down should exit quietly if the vm shut down successfully. If it didn't it'll still timeout.