Kevin Jackson

Just a note on this. This repo that supported the book that was published a few years ago, and for the release of OpenStack at the time, has been unmaintained...

Is it possible to provide more of the logs rather than the summary? The error is likely to (or I'm hoping) to show earlier on up the log output. Thanks!

Thanks for raising this - I'll run through things as soon as possible and report back.

Weird. The script does nothing unusual - just executes openstack commands as user. However I can confirm the problem and where it is. The script first creates a flat network...

Unfortunately no - I got completely distracted away from this issue. I'll troubleshoot further tomorrow and report back. From the original troubleshooting it doesn't make sense. I've put time aside...

I've been working on this but can't get past the fact I can see when it changes - it is (and a correction to the above) specifically after the subnet...

It occurs when you run this specific command which puts the subnet onto the Flat network openstack subnet create --project admin --subnet-range 192.168.100.0/24 --dhcp --dns-nameserver 192.168.1.1 --gateway 192.168.1.1 --allocation-pool start=192.168.100.100,end=192.168.100.250...

We don't control the Vagrant boxes - we just use them for our environment. See here: https://app.vagrantup.com/velocity42/boxes/xenial64 - this box still appears to be accessible - could it be a...

I think this is a Vagrant version problem. The previous method to become root was marked as deprecated in a later version of Ansible, and we've been using Vagrant 2.X...

Nice catch there. I'm currently using openstack@vagrant:~$ vagrant --version Vagrant 2.0.2 I'm away until the end of the week to make any changes but please test a different version.