Skip to content
This repository has been archived by the owner on Jun 28, 2024. It is now read-only.

No straightforward way to clean up after failed "vagrant up" #3757

Closed
dgibson opened this issue Jul 27, 2021 · 1 comment · Fixed by #3965
Closed

No straightforward way to clean up after failed "vagrant up" #3757

dgibson opened this issue Jul 27, 2021 · 1 comment · Fixed by #3965
Assignees
@wainersm
Labels
area/ci bug Incorrect behaviour

Comments

@dgibson
Copy link
Contributor

dgibson commented Jul 27, 2021

Description of problem

Sometimes vagrant up fails, and when it does it's not at all clear how to clean up to try again.

Expected result

Working instructions in README.md to remove a failed vagrant up install.

Actual result

After a failed vagrant up, I tried:

  • Retrying vagrant up directly
$ vagrant up fedora
Bringing machine 'fedora' up with 'libvirt' provider...
==> fedora: Running action triggers before up ...
==> fedora: Running trigger...
==> fedora: Checking if box 'fedora/32-cloud-base' version '32.20200422.0' is up to date...
Name `tests_fedora` of domain about to create is already taken. Please try to run
`vagrant up` command again.
  • vagrant destroy
$ vagrant destroy fedora
Name `tests_fedora` of domain about to create is already taken. Please try to run
`vagrant up` command again.

Further information

The only way I've yet found to return to a clean state is this complicated procedure (some steps may be unnecessary depending on exactly when/how the vagrant up failed:

$ git clean -fdx
$ rm -rf ~/.vagrant.d
$ virsh destroy tests_fedora
$ virsh undefine tests_fedora
@dgibson dgibson added bug Incorrect behaviour needs-review Needs to be assessed by the team. labels Jul 27, 2021
@dgibson
Copy link
Contributor Author

dgibson commented Jul 27, 2021

@marcel-apf for your attention.

@c3d c3d added area/ci and removed needs-review Needs to be assessed by the team. labels Aug 3, 2021
wainersm added a commit to wainersm/kc-tests that referenced this issue Sep 13, 2021
@wainersm
ci: Introduce the vagrant-cleaner.sh script
7946dff 
The vagrant configuration sometimes can get into inconsistent state. For
instance, the domain on libvirt was created by the framework that thinks
the box is not initialized yet. Or eventually the developer wants to
simply wipe out all vagrant files and created resources from his/her
workstation.

In this commit it was introduced the vagrant-cleaner.sh script which
aims on help developers to clean up the vagrant stuffs.

Fixes kata-containers#3757
Signed-off-by: Wainer dos Santos Moschetta <[email protected]>
wainersm added a commit to wainersm/kc-tests that referenced this issue Sep 14, 2021
@wainersm
ci: Introduce the vagrant-cleaner.sh script
2fdad3b 
The vagrant configuration sometimes can get into inconsistent state. For
instance, the domain on libvirt was created by the framework that thinks
the box is not initialized yet. Or eventually the developer wants to
simply wipe out all vagrant files and created resources from his/her
workstation.

In this commit it was introduced the vagrant-cleaner.sh script which
aims on help developers to clean up the vagrant stuffs.

Fixes kata-containers#3757
Signed-off-by: Wainer dos Santos Moschetta <[email protected]>
@wainersm wainersm mentioned this issue Sep 14, 2021
Merged
wainersm added a commit to wainersm/kc-tests that referenced this issue Sep 20, 2021
@wainersm
ci: Introduce the vagrant-cleaner.sh script
0f0610b 
The vagrant configuration sometimes can get into inconsistent state. For
instance, the domain on libvirt was created by the framework that thinks
the box is not initialized yet. Or eventually the developer wants to
simply wipe out all vagrant files and created resources from his/her
workstation.

In this commit it was introduced the vagrant-cleaner.sh script which
aims on help developers to clean up the vagrant stuffs.

Fixes kata-containers#3757
Signed-off-by: Wainer dos Santos Moschetta <[email protected]>
@dgibson dgibson linked a pull request Sep 27, 2021 that will close this issue
Vagrant: boot q35 machine and other improvements #3965
Merged
wainersm added a commit to wainersm/kc-tests that referenced this issue Oct 27, 2021
@wainersm
ci: Introduce the vagrant-cleaner.sh script
fa7fcf2 
The vagrant configuration sometimes can get into inconsistent state. For
instance, the domain on libvirt was created by the framework that thinks
the box is not initialized yet. Or eventually the developer wants to
simply wipe out all vagrant files and created resources from his/her
workstation.

In this commit it was introduced the vagrant-cleaner.sh script which
aims on help developers to clean up the vagrant stuffs.

Fixes kata-containers#3757
Signed-off-by: Wainer dos Santos Moschetta <[email protected]>
wainersm added a commit to wainersm/kc-tests that referenced this issue Oct 28, 2021
@wainersm
ci: Introduce the vagrant-cleaner.sh script
0338d24 
The vagrant configuration sometimes can get into inconsistent state. For
instance, the domain on libvirt was created by the framework that thinks
the box is not initialized yet. Or eventually the developer wants to
simply wipe out all vagrant files and created resources from his/her
workstation.

In this commit it was introduced the vagrant-cleaner.sh script which
aims on help developers to clean up the vagrant stuffs.

Fixes kata-containers#3757
Signed-off-by: Wainer dos Santos Moschetta <[email protected]>
wainersm added a commit to wainersm/kc-tests that referenced this issue Nov 4, 2021
@wainersm
ci: Introduce the vagrant-cleaner.sh script
b349f56 
The vagrant configuration sometimes can get into inconsistent state. For
instance, the domain on libvirt was created by the framework that thinks
the box is not initialized yet. Or eventually the developer wants to
simply wipe out all vagrant files and created resources from his/her
workstation.

In this commit it was introduced the vagrant-cleaner.sh script which
aims on help developers to clean up the vagrant stuffs.

Fixes kata-containers#3757
Signed-off-by: Wainer dos Santos Moschetta <[email protected]>
wainersm added a commit to wainersm/kc-tests that referenced this issue Nov 11, 2021
@wainersm
ci: Introduce the vagrant-cleaner.sh script
3c62af2 
The vagrant configuration sometimes can get into inconsistent state. For
instance, the domain on libvirt was created by the framework that thinks
the box is not initialized yet. Or eventually the developer wants to
simply wipe out all vagrant files and created resources from his/her
workstation.

In this commit it was introduced the vagrant-cleaner.sh script which
aims on help developers to clean up the vagrant stuffs.

Fixes kata-containers#3757
Signed-off-by: Wainer dos Santos Moschetta <[email protected]>
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@wainersm wainersm

Labels
area/ci bug Incorrect behaviour
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Vagrant: boot q35 machine and other improvements wainersm/kc-tests
3 participants
@dgibson @wainersm @c3d