Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cannot restore snapshot for particular machine in conjunction with --provision-with option #8994

Closed
zofrex opened this issue Sep 24, 2017 · 3 comments
Labels

Comments

@zofrex
Copy link

zofrex commented Sep 24, 2017

Vagrant version

2.0.0

Host operating system

macOS Sierra 10.12.6

Guest operating system

N/A

Vagrantfile

N/A

Debug output

N/A

Expected behavior

Restore the snapshot "preupgrade" for the machine "webserver"

Actual behavior

Complained that no machine named "preupgrade" exists:

The machine with the name 'preupgrade' was not found configured for
this Vagrant environment.

Steps to reproduce

$ vagrant snapshot restore --provision-with sync-clock webserver preupgrade

Where "webserver" is the name of a Vagrant machine and "preupgrade" is the name of a snapshot:

$ vagrant snapshot list webserver
preupgrade

In case the order is wrong I also tried the following:

vagrant snapshot restore --provision-with sync-clock preupgrade webserver

vagrant snapshot restore --provision-with sync-clock preupgrade

All have the same result.

@briancain briancain added the core label Sep 25, 2017
@ropbear
Copy link

ropbear commented Aug 23, 2018

Vagrant version

2.1.2

Host OS

Windows 10 1809

Steps to reproduce

vagrant up --provision-with <provisioner1>
vagrant snapshot save <machine> <snapshot>
vagrant snapshot restore <machine> <snapshot> --provision-with <provisioner2>

Expected result

provisioner1 is ran the first time, and upon restoring the snapshot provisioner2 is ran but not provisioner1

Actual result

Upon restoring the snapshot, I recieve The machine with the name <snapshot> was not found configured for this Vagrant environment.

@chrisroberts
Copy link
Member

Fixed via #10490

@ghost
Copy link

ghost commented Mar 28, 2020

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.

@ghost ghost locked and limited conversation to collaborators Mar 28, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

4 participants