I am in agreement and extremely disappointed that I paid for a course, specifically to use the labs, and it cannot be used.  If they cannot be corrected now then everyone that has paid for the course should be reimbursed.

Sounds like this has been a long-term issue...I'm seeing the same many months later...guess it's not just me lol

I took this course to potentially help with teaching the skills and tools necessary for this kind of troubleshooting because I've been trying to set up OpenStack by myself using devstack as a playground but these kinds of issues are very common when playing with OpenStack; so common and so time-consuming, in fact, that I figured a Linux Foundation course on the topic may help out but it looks to be the same thing even when experts are trying to setup simple sandboxes for instructional purposes.

If nothing else, to all the other students: if you're having these kinds of issues, congratulations, you are one step closer to learning what managing an OpenStack cloud is really like

That being said, it looks like the labs are potentially useless and at best running through the course material may provide some useful information but in terms of practical experience self-guided tinkering is still the way to go...

Here it is:

[[local|localrc]]
HOST_IP=172.17.0.27
FLAT_INTERFACE=ens3
FIXED_RANGE=10.4.128.0/20
FIXED_NETWORK_SIZE=4096
FLOATING_RANGE=192.168.42.128/25
MULTI_HOST=1
LOGFILE=/opt/stack/logs/stack.sh.log
ADMIN_PASSWORD=openstack
DATABASE_PASSWORD=db-secret
RABBIT_PASSWORD=rb-secret
SERVICE_PASSWORD=sr-secret

Use the following to explore new project

enable_plugin barbican https://git.openstack.org/openstack/barbican stable/pike

there are some errors in the logfile:
error: 'Access denied for user 'root'@'localhost' (using password: YES)'
2018-09-10 16:27:42.177 | Job for devstack@etcd.service failed because the control process exited with error code. See "systemctl status devstack@
etcd.service" and "journalctl -xe" for details.
2018-09-10 16:27:42.188 | +lib/etcd3:start_etcd3:1 exit_trap
2018-09-10 16:27:42.198 | +./stack.sh:exit_trap:521 local r=1
2018-09-10 16:27:42.208 | ++./stack.sh:exit_trap:522 jobs -p
2018-09-10 16:27:42.218 | +./stack.sh:exit_trap:522 jobs=
2018-09-10 16:27:42.226 | +./stack.sh:exit_trap:525 [[ -n '' ]]
2018-09-10 16:27:42.234 | +./stack.sh:exit_trap:531 '[' -f /tmp/tmp.kT3QlJM79D ']'
2018-09-10 16:27:42.244 | +./stack.sh:exit_trap:532 rm /tmp/tmp.kT3QlJM79D
2018-09-10 16:27:42.255 | +./stack.sh:exit_trap:536 kill_spinner
2018-09-10 16:27:42.264 | +./stack.sh:kill_spinner:417 '[' '!' -z '' ']'
2018-09-10 16:27:42.274 | +./stack.sh:exit_trap:538 [[ 1 -ne 0 ]]
2018-09-10 16:27:42.282 | +./stack.sh:exit_trap:539 echo 'Error on exit'
2018-09-10 16:27:42.282 | Error on exit
2018-09-10 16:27:42.293 | +./stack.sh:exit_trap:541 type -p generate-subunit
2018-09-10 16:27:42.302 | +./stack.sh:exit_trap:542 generate-subunit 1536596605 257 fail
2018-09-10 16:27:42.730 | +./stack.sh:exit_trap:544 [[ -z /opt/stack/logs ]]
2018-09-10 16:27:42.738 | +./stack.sh:exit_trap:547 /home/ubuntu/devstack/tools/worlddump.py -d /opt/stack/logs
2018-09-10 16:27:43.569 | +./stack.sh:exit_trap:556 exit 1

I did reboot and start over no change, but can do again...

Thanks Tim,
Yes that line was commented out, I must have copied it from the screen skipping the hash.
I re-did the install and now I have access to the BUI (w/o permission to the dashboard is that expected?). Hopefully things will go smoother now.