[CentOS-devel] 'vagrant up' not working after yum update
Dharmit Shah
dshah at redhat.comThu May 19 11:37:54 UTC 2016
- Previous message: [CentOS-devel] 'vagrant up' not working after yum update
- Next message: [CentOS-devel] CentOS PaaS SIG meeting (2016-05-18)
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On 05/18/2016 08:38 PM, Dominic Cleal wrote: > On 18/05/16 15:52, Dharmit Shah wrote: >> Hello all, >> >> I'm seeing this behaviour since I did `yum update` today on one of my >> CentOS 7 boxes in that, `vagrant up` for libvirt provider throws the error: >> >> "The provider 'libvirt' could not be found, but was requested to >> back the machine 'default'. Please use a provider that exists." >> >> Details of the issue can be found on [1]. I observed the issue when I >> was doing testing for Atomic Developer Bundle (ADB) [2]. > > Could you try this newer build of sclo-vagrant1-vagrant (the -5 > release)? http://cbs.centos.org/koji/buildinfo?buildID=11113 > Yes, it works now. Thanks Dominic! Regards, Dharmit.
- Previous message: [CentOS-devel] 'vagrant up' not working after yum update
- Next message: [CentOS-devel] CentOS PaaS SIG meeting (2016-05-18)
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the CentOS-devel mailing list