[Pulp-dev] Vagrant Up is Broken (and how to workaround it)

[Brian Bouterse]

When running `vagrant up` it will get stuck early on with the output: "==>
dev: Installing NFS client..." and will eventually error out. This happens
100% of the time and started about 2 days ago.

A recent version of rpcbind that was pushed to Fedora 24+ introduced a
regression. That issue is tracked in this BZ [0]. Thanks to @dalley for
helping to identify it as a related BZ.

I tried the workaround from Comment 20 on the BZ and with help from
@sysadmind, @smyers, @dalley, and @dkliban on IRC it works! Instead of
`vagrant up` do this:

1. Do your normal `vagrant up`
2. Wait for it get stuck
3. Ctrl-C, Ctrl-C to do an immediate exit of vagrant
4. `vagrant ssh` to ssh in to your guest and run these commands

sudo su
mkdir -p /etc/systemd/system/rpcbind.service.d/
cat << EOF > /etc/systemd/system/rpcbind.service.d/tmpfiles-setup.conf
[Unit]
Wants=systemd-tmpfiles-setup.service
After=systemd-tmpfiles-setup.service
EOF
exit

5. Run `vagrant reload`
6. Watch vagrant complete without error

I don't think we should automate this because it should be resolved soon.
This BZ is getting a lot of attention. Other thoughts or ideas are welcome.

[0]: https://bugzilla.redhat.com/show_bug.cgi?id=1401561

-Brian
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/pulp-dev/attachments/20170124/ef407d74/attachment.htm>