Comment 4 for bug 1561250

Unfortunately the above-mentioned fix is not possible when your Vagrantfile contains extra network configuration. In those cases, you get something like this before you get a chance to update the hosts file:

    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:

    sudo: unable to resolve host ubuntu-xenial
    mesg: ttyname failed: Inappropriate ioctl for device

This renders the image useless to many who want to use it with a non-trivial Vagrantfile.