Hi,
I wanted to try vagrant box of Centos7 for my vm but I encounter problems during setting up a vm.
I did very basic setup, in empty folder I did ``` vagrant init centos/7 vagrant up ```
In a result it repetitively promts ``` default: Warning: Authentication failure. Retrying... ```
Full output here: http://pastebin.com/JrQHER6L I am using Linux Mint 17.3 with VirtualBox 5 and Vagrant 1.8.5.
Any clues what's going on wrong here?
Best, Rafal
P.S. I am sorry if I doubled the email, I don't know if it get through on the first time before I registered to the mailing list.
On Fri, Aug 5, 2016 at 7:35 AM, Rafal Skolasinski <r.j.skolasinski@gmail.com
wrote:
Hi,
I wanted to try vagrant box of Centos7 for my vm but I encounter problems during setting up a vm.
I did very basic setup, in empty folder I did
vagrant init centos/7 vagrant upIn a result it repetitively promts
default: Warning: Authentication failure. Retrying...Full output here: http://pastebin.com/JrQHER6L I am using Linux Mint 17.3 with VirtualBox 5 and Vagrant 1.8.5.
Yes, this looks a lot like a Vagrant bug that was introduced in 1.8.5: https://github.com/mitchellh/vagrant/issues/7610
It should be fixed in 1.8.6 whenever that's released, but there are some workarounds in the ticket in the meantime.
-Jeff
Thanks! I switched to Vagrant 1.8.4 for a meantime and everything works fine!
Cheers, Rafal
On 5 August 2016 at 16:38, Jeff Sheltren jeff@tag1consulting.com wrote:
On Fri, Aug 5, 2016 at 7:35 AM, Rafal Skolasinski < r.j.skolasinski@gmail.com> wrote:
Hi,
I wanted to try vagrant box of Centos7 for my vm but I encounter problems during setting up a vm.
I did very basic setup, in empty folder I did
vagrant init centos/7 vagrant upIn a result it repetitively promts
default: Warning: Authentication failure. Retrying...Full output here: http://pastebin.com/JrQHER6L I am using Linux Mint 17.3 with VirtualBox 5 and Vagrant 1.8.5.
Yes, this looks a lot like a Vagrant bug that was introduced in 1.8.5: https://github.com/mitchellh/vagrant/issues/7610
It should be fixed in 1.8.6 whenever that's released, but there are some workarounds in the ticket in the meantime.
-Jeff
CentOS-devel mailing list CentOS-devel@centos.org https://lists.centos.org/mailman/listinfo/centos-devel
On 05/08/16 15:58, Rafal Skolasinski wrote:
Thanks! I switched to Vagrant 1.8.4 for a meantime and everything works fine!
thanks for working through this, but make sure you leave feedback on the bug report!
Hi,
I am not sure I get what bug report you have in mind, problem was with Vagrant and according to the issue it's already fixed in the master and will be fixed in 1.8.6 release.
Cheers, Rafal
On 6 August 2016 at 13:31, Karanbir Singh mail-lists@karan.org wrote:
On 05/08/16 15:58, Rafal Skolasinski wrote:
Thanks! I switched to Vagrant 1.8.4 for a meantime and everything works fine!
thanks for working through this, but make sure you leave feedback on the bug report!
-- Karanbir Singh +44-207-0999389 | http://www.karan.org/ | twitter.com/kbsingh GnuPG Key : http://www.karan.org/publickey.asc _______________________________________________ CentOS-devel mailing list CentOS-devel@centos.org https://lists.centos.org/mailman/listinfo/centos-devel
On 8/6/16, Karanbir Singh mail-lists@karan.org wrote:
thanks for working through this, but make sure you leave feedback on the bug report!
I assume you mean feedback on Vagrant bug #7610, helpfully linked to by Jeff? Seth blocked all further feedback on this bug on July 22. [1]
To put it diplomatically, I'm stunned that a bug of this magnitude not only made it into a release (don't they even try to create a new box with "vagrant up" before publising a _stable_ release?), but also that there's still no 1.8.6 release, 19 days after the bug was filed. There's not even a mention of this bug on the upstream download page, and their official documentation warns against using distribution packages, in pretty strong terms but without any explanation (yes, really). [2]
There's always the possibility for distros to add a custom patch to their Vagrant 1.8.5 packages. SCL only seems to package Vagrant 1.7 right now, so I guess this isn't an issue when using CentOS as a host. I should have updated the release notes for our existing Vagrant images to mention this bug, instead of just mentioning it in the release notes for v1607 (not yet published).
Regards, Laurențiu
[1] https://github.com/mitchellh/vagrant/issues/7610#issuecomment-234609660 [2] https://www.vagrantup.com/docs/installation/
----- Original Message -----
From: "Laurențiu Păncescu" lpancescu@gmail.com To: "The CentOS developers mailing list." centos-devel@centos.org Sent: Saturday, August 6, 2016 8:18:16 PM Subject: Re: [CentOS-devel] Problem with vagrant box (ssh-ing during ``vagrant up`` doesn't work)
I assume you mean feedback on Vagrant bug #7610, helpfully linked to by Jeff? Seth blocked all further feedback on this bug on July 22. [1]
To put it diplomatically, I'm stunned that a bug of this magnitude not only made it into a release (don't they even try to create a new box with "vagrant up" before publising a _stable_ release?), but also that there's still no 1.8.6 release, 19 days after the bug was filed. There's not even a mention of this bug on the upstream download page, and their official documentation warns against using distribution packages, in pretty strong terms but without any explanation (yes, really). [2]
There's always the possibility for distros to add a custom patch to their Vagrant 1.8.5 packages. SCL only seems to package Vagrant 1.7
There will be an SCL update to 1.8.5 (patched) soon.
right now, so I guess this isn't an issue when using CentOS as a host. I should have updated the release notes for our existing Vagrant images to mention this bug, instead of just mentioning it in the release notes for v1607 (not yet published).
Regards, Laurențiu
[1] https://github.com/mitchellh/vagrant/issues/7610#issuecomment-234609660 [2] https://www.vagrantup.com/docs/installation/ _______________________________________________ CentOS-devel mailing list CentOS-devel@centos.org https://lists.centos.org/mailman/listinfo/centos-devel
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
On 08/08/16 11:01, Pavel Valena wrote:
----- Original Message -----
There's always the possibility for distros to add a custom patch to their Vagrant 1.8.5 packages. SCL only seems to package Vagrant 1.7
There will be an SCL update to 1.8.5 (patched) soon.
That's great to hear. Is there an automatic testing system for SCL packages? Perhaps something like Jenkins in Fedora and CentOS - not sure how extensive the tests are, though... it probably varies per package.
Regards, Laurențiu
----- Original Message -----
From: "Laurentiu Pancescu" lpancescu@gmail.com To: "The CentOS developers mailing list." centos-devel@centos.org Sent: Monday, August 8, 2016 11:31:23 AM Subject: Re: [CentOS-devel] Problem with vagrant box (ssh-ing during ``vagrant up`` doesn't work)
That's great to hear. Is there an automatic testing system for SCL packages? Perhaps something like Jenkins in Fedora and CentOS - not sure how extensive the tests are, though... it probably varies per package.
Yes, there is Jenkins CI[1], but I am afraid the tests are still failing, as I didn't yet got time to fix them.
Test sources[2] are available for anyone who wishes to fix them:).
[1] https://ci.centos.org/view/SCLo/job/SCLo-sclo-vagrant1-sclo-C7-x86_64/ [2] https://github.com/sclorg/sclo-ci-tests/tree/master/collections/sclo-vagrant...
Regards, Laurențiu _______________________________________________ CentOS-devel mailing list CentOS-devel@centos.org https://lists.centos.org/mailman/listinfo/centos-devel
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
On 09/08/16 19:38, Pavel Valena wrote:
Yes, there is Jenkins CI[1], but I am afraid the tests are still failing, as I didn't yet got time to fix them.
Test sources[2] are available for anyone who wishes to fix them:).
[1] https://ci.centos.org/view/SCLo/job/SCLo-sclo-vagrant1-sclo-C7-x86_64/ [2] https://github.com/sclorg/sclo-ci-tests/tree/master/collections/sclo-vagrant...
From the error log [3], I'd guess KVM isn't working on the test host. Is virtualization enabled in the BIOS? Or maybe the kvm_intel module needs to be loaded with nested=Y, if the host itself is a KVM guest (as opposed to a bare-metal server)? Does it work if you add 'libvirt.provider = qemu' to the Vagrantfile?
Regards, Laurențiu
[3] https://ci.centos.org/view/SCLo/job/SCLo-sclo-vagrant1-sclo-C7-x86_64/lastUn...
-
Jeff Sheltren -
Karanbir Singh -
Laurențiu Păncescu -
Pavel Valena -
Rafal Skolasinski