Bug 2132090

Summary:	Vagrant-libvirt: Bringing up several boxes fails sometimes with HandleBox not defined
Product:	[Fedora] Fedora	Reporter:	Mattias Bengtsson <mattias.jc.bengtsson>
Component:	vagrant-libvirt	Assignee:	Vít Ondruch <vondruch>
Status:	CLOSED DUPLICATE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	37	CC:	jprokop, lmohanty, madam, pvalena, strzibny, tadej.j, thrcka, vondruch
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2023-05-22 09:34:13 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Mattias Bengtsson 2022-10-04 15:27:16 UTC

Description of problem:

I run into this issue several times a day:
- https://github.com/vagrant-libvirt/vagrant-libvirt/issues/1445

This is fixed in this PR:
- https://github.com/vagrant-libvirt/vagrant-libvirt/pull/1485

Version-Release number of selected component (if applicable):

vagrant-libvirt-0.7.0-4.fc37.noarch

How reproducible:

Sometimes. It's probably a race condition as noted in the referenced bug above.

Steps to Reproduce:
1. Create a Vagrantfile that starts several boxes
2. Run vagrant up
3. Try #2 until you get:

    constant VagrantPlugins::ProviderLibvirt::Action::HandleBox not defined

Actual results:

I get:
    constant VagrantPlugins::ProviderLibvirt::Action::HandleBox not defined
and one of the boxes doesn't start.

Expected results:

All to always start.

Additional info:

Fixed upstream. My suggestion is to cherrypick the fix or to just upgrade vagrant-libvirt.

Comment 1 Mattias Bengtsson 2023-01-11 18:21:00 UTC

I would say that this depends on https://bugzilla.redhat.com/show_bug.cgi?id=2075223.

Comment 2 Jarek Prokop 2023-05-22 09:34:13 UTC

This bug seems to describe the same issue as rhbz#2100543

*** This bug has been marked as a duplicate of bug 2100543 ***