Hello, Yes, I have the sclo-vagrant1 collection mostly updated offline. There are few bugs to solve, but then I will build it in for CentOS. Foremost change is, that it's going to be based on Ruby 2.3 collection. ----- Original Message ----- > From: "Jeff Sheltren" <jeff at tag1consulting.com> > To: "The CentOS developers mailing list." <centos-devel at centos.org> > Sent: Friday, January 20, 2017 3:28:15 PM > Subject: Re: [CentOS-devel] Any plans to update sclo-vagrant1? > > On Fri, Jan 20, 2017 at 3:20 AM, Laurentiu Pancescu < lpancescu at gmail.com > > wrote: > > > If you'd rather update to a newer version, Vagrant 1.9.1 broke at least > private networking (eth0 is preconfigured by our image, but the additional > network interfaces that Vagrant 1.9.1 configures don't get an IP address - I > assume public networking is broken as well, but I only tried private > networking). I also saw some entries concerning NFS in the upstream issue > tracker, not sure if it's caused by the same bug. Versions 1.9.0 and 1.8.6 > work for me. I will stick with(or move to) patched and working version in Fedora[1]. As of now, it is Vagrant 1.8.7. [1] https://koji.fedoraproject.org/koji/packageinfo?packageID=19808 > > > I believe you're referring to this bug in Vagrant 1.9.1 ( > https://github.com/mitchellh/vagrant/issues/8166 ) which also links out to > some other related/duplicate issues. FWIW, it appears a manual 'service > network restart' will load the network interfaces that get disabled by > Vagrant. At least that worked for me, obviously not ideal though. Sadly > there seem to be quite a few "breaking" issues in recent Vagrant releases, > seemingly due to lack of testing upstream :( They do get fixed, but it can > take weeks for new releases to be pushed including the fix. > > -Jeff > I will keep you posted, so we can test and fix in advance any issues to come. Regards, Pavel Valena Associate Software Engineer Brno, Czech Republic RED HAT | TRIED. TESTED. TRUSTED. All of the airlines in the Fortune Global 500 rely on Red Hat. Find out why at Trusted | Red Hat <http://www.redhat.com/en/about/trusted>