search

stackinabox / vagrant-opdk-box

Cloud in a box. OpenStack, Docker, UrbanCode Deploy & Patterns (HEAT Designer)
Apache License 2.0
5 stars 4 forks source link

Problem booting machine on vagrant 1.8.1 #6

Open mdelder opened 8 years ago

mdelder commented 8 years ago

I encountered the following error message with the latest as of 9/5/2016 using vagrant 1.8.1.

==> openstack: Machine booted and ready!
==> openstack: Checking for guest additions in VM...
==> openstack: Checking for host entries
==> openstack: Configuring and enabling network interfaces...
The following SSH command responded with a non-zero exit status.
Vagrant assumes that this means the command failed!

/sbin/ifdown eth1 2> /dev/null

Stdout from the command:

Stderr from the command:

mesg: ttyname failed: Inappropriate ioctl for device

I found some Google responses that alluded to problems due to network adapter shifts on the latest Ubuntu. I upgraded to vagrant 1.8.5 and continued to see the following message: 

==> openstack: mesg: ttyname failed: Inappropriate ioctl for device

However, the provisioning continued.

Recommend specifying a table with supported versions for VirtualBox, Vagrant, and Docker.

tpouyer commented 8 years ago

So this is a know bug in vagrant specifically regarding the Ubuntu 16.04 based vagrant boxes. I ran into the same problem about a month ago. I can add a version check for vagrant in the vagrantfile.

Your last issue is a little more difficult. Like you said it does not cause any problems but for a new or unfamiliar user it would probably cause some concern. I'll have to dig into that a bit more to get an answer for that.