Closed mloskot closed 1 year ago
Hi there,
Would you please provide a gist of the debug output from running vagrant plugin install vagrant-reload --debug
.
Thanks!
Hi @chrisroberts, I assume you mean to collect the debug output on machine upgraded to Vagrant 2.3.6, correct?
Yes, that is correct
Possibly related to https://github.com/hashicorp/vagrant/issues/13177
@StephenPooley Your report looks like exactly the problem. I did not have a chance to collect the debug output as it needs upgrading to broken environment, while I need a working environment ATM :)
@mloskot Agree. Upgrading to a broken environment does sound like a nugatory activitiy and this problem is really easy to reproduce. I feel that the information to reproduce and the debug output is included in https://github.com/hashicorp/vagrant/issues/13177 In summary install vagrant v2.3.6 on 64bit Windows and try to work with a plugin (e.g. vmware_desktop). The problem also does appear to be the same as previously discussed in https://github.com/hashicorp/vagrant-installers/pull/270 and https://github.com/hashicorp/vagrant/issues/13156. It does appear that both the problem and the fix are well understood. Over to you @chrisroberts
@mloskot Inspecting the 64 bit Windows package, the cacert file is unexpectedly missing. I'm looking through the build process to determine why it wasn't included as it was properly installed in dev builds prior to release.
Downloading the cacert.pem file and dropping it in C:\HashiCorp\Vagrant\embedded\cacert.pem
or setting the SSL_CERT_FILE
environment variable to the download path should provide an immediate fix.
The winrm issues were introduced from openssl deprecating engines and replacing them with providers (along with marking MD4
as legacy and not loading it by default). The Ruby openssl library provides no method for loading in the way it was previously available with engines. #13178 provides a way around this so legacy and default providers get loaded.
This development build includes both the missing cacert file and the update for handling openssl 3 discussed in this issue.
@chrisroberts Thank you for your updates, much appreciated. I will try to pick it up later this week or next week.
I upgraded two machines on Windows 11 to from Vagrant 2.3.4 to 2.3.6 and machines that used to work fine simply stopped working.
First, selection of pugins required by https://github.com/kubernetes-sigs/sig-windows-dev-tools/ i.e.
vagrant-reload vagrant-vbguest winrm winrm-elevated
stopped working and upgrading due to https://github.com/hashicorp/vagrant/issues/13156, so I had to apply the workaround:Second, well-known Windows Server boxes that used to work, stopped booting:
After downgrading to 2.3.4, everything is back to order: