Vagrant: Vagrant fails on destroy

[Occams]

Vagrant version

2.0.1

Host operating system

Windows Server 2016
Virtualbox 5.1.30

Guest operating system

Windows 10 Fall Creators Update

Debug output

https://gist.github.com/Occams/a849f8e10ad413cfdc3e29e6746fe791

This issue popped up on a CI-Build doing automated testing using vagrant. Unfortunately, there's no way for me to reproduce this bug and provide more detailed debug information.

[briancain]

@Occams - Does your CI do any cleanup prior to running vagrant destroy? It looks like maybe a folder within a vagrant environment got deleted, and then when vagrant destroy was invoked it tried to read a folder that it expected to exist on disk, but was returned as nil because it was no longer there.

[Occams]

@briancain There's no cleanup involved at this stage. All automated tests are conducted in a pristine and temporary vagrant environment. The sequence of vagrant commands is quite simple:

• Dynamically generate Vagrant file

• Do a vagrant up

• Create a live snapshot using vagrant snapshot push

• Invoke automated tests via sequences of vagrant snapshot pop and vagrant powershell

• Cleanup using vagrant destroy --force

We run hundreds of successful tests each day, thus this must be some kind of race condition.

[chrisroberts]

@Occams Are you still encountering this issue with the latest Vagrant release?

[briancain]

Hey there,

I am going to close this due to lack of response. If this is still occurring, please open a new issue and follow the provided issue template that appears when you click the "New Issue" button. This will help us in getting a reproduction and fix. Thanks!

[Occams]

I'm terribly sorry, this issue seems to have slipped my attention. We're currently not encountering this issue on Vagrant 2.1.5

[hashibot[bot]]

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.