Skip to content

beaker always assumes libvirtd for vagrant, even when vagrant is requested #438

Description

@bastelfreak

In https://github.com/voxpupuli/beaker-hostgenerator/blob/master/lib/beaker-hostgenerator/hypervisor/vagrant.rb#L38 , we hardcode a URL schema:

base_config['box_url'] = "https://cloud.centos.org/centos/#{version}-stream/x86_64/images/CentOS-Stream-Vagrant-#{version}-latest.x86_64.vagrant-libvirt.box"

beaker supports different hypervisors, one is vagrant, another one is vagrant_libvirt. For historic reasons, the vagrant hypervisor always used virtualbox. This breaks now, because the libvirt image isn't suitable for virtualbox.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions