No passwd entry for user 'vagrant' when vagrant up

[Liping Mao]

I get the following error when vagrant up with ubuntu/xenial64, I'm using version '20170328.0.0'

==> default: Get:31 http://archive.ubuntu.com/ubuntu xenial-backports/universe amd64 Packages [2,512 B]
==> default: Get:32 http://archive.ubuntu.com/ubuntu xenial-backports/universe Translation-en [1,216 B]
==> default: Fetched 11.5 MB in 47s (242 kB/s)
==> default: Reading package lists...
==> default: No passwd entry for user 'vagrant'
==> default: No passwd entry for user 'vagrant'
The SSH command responded with a non-zero exit status. Vagrant
assumes that this means the command failed. The output for this command
should be in the log above. Please read the output to determine what
went wrong.

I find the following bug in cloud-images:
https://bugs.launchpad.net/cloud-images/+bug/1569237

Looks like others also get problem when use vagrant to start up ubuntu/xenial64.
In that bug, there is workaround to create vagrant user:
https://github.com/joelhandwell/ubuntu_vagrant_boxes/blob/master/u16/Vagrantfile

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/461207
Committed: https://git.openstack.org/cgit/openstack/kuryr-libnetwork/commit/?id=ea12e966eeb599524454a7e5ec49dfbd24b83610
Submitter: Jenkins
Branch: master

commit ea12e966eeb599524454a7e5ec49dfbd24b83610
Author: Liping Mao (limao) <email address hidden>
Date: Sat Apr 29 21:55:51 2017 +0800

    Fix vagrant up with ubuntu/xenial64

    There is the following bug in ubuntu/xenial64 cloud image.
    https://bugs.launchpad.net/cloud-images/+bug/1569237
    This will cause that vagrant user will not exist.

    Change-Id: Iacc4135fa165d8624ad61c4e5170683180234cbf
    Closes-Bug: #1687197

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/kuryr-libnetwork 0.2.0 release.