sunbeam cluster bootstrap --accept-defaults hangs

[Nicholas Papadonis]

I followed the official instructions at:

https://ubuntu.com/openstack/install

I'm using VirtualBox 7.0.8 w/ nested support and Ubuntu Server 22.04.2 and am noting hangs/failures during the step to Bootstrap the cloud. I allocated 16GB RAM and 4 CPUs to the Ubuntu VM.

On Host:

$ ./VBoxManage modifyvm ubuntu22 --nested-hw-virt on

On Ubuntu Server VM:

$ sunbeam prepare-node-script | bash -x && newgrp snap_daemon

works

$ sunbeam cluster bootstrap --accept-defaults

hangs, specifically at "Deploying OpenStack Control Plane to Kubernetes".

I had to abort the script. I also note, that I did not run this step as sudo root.

I try to re-run the above bootstrap and receive:

db_root: cannot open: /etc/target

Finally I get the response:

Node has been bootstrapped with roles: control, compute

I then invoke the next command:

$ sunbeam configure --accept-defaults --openrc demo-openrc

and receive another error.

A strack trace appears noting a non-zero exit status 1 on the command /snap/openstack/182/bin/terraform apply -auto-approve -nocolor -parrallelism=1.

I'm wondering if this is a problem with the installation scripts, version mismatch or VirtualBox itself.

Thanks

[Nicholas Papadonis (atod)]

More details:
Error: Error creating OpenStack compute client: Get "http://10.20.21.10:80/openstack-keystone/": OpenStack connection error, retries exhausted. Aborting.

So I see there is a network problem commenting with Keystone. How should I debug this? What may be differing in my configuration to cause such an error?

[Nicholas Papadonis (atod)]

Where is the 10.20.21.10 ip address coming from?

I don't see any network using "ip a" with that address range.

[Nicholas Papadonis (atod)]

I also try re-running:

$ sunbeam cluster bootstrap --accept-defaults

and get the error

Error: Leader for application 'mysql' is missing from model 'openstack'

[Tim Rogers (alphabeta6)]

I had the same issue. Fixed via: chmod 644 ~/.ssh/authorized_keys
For some reason mine was set to 664 and owned as $USER:snap_daemon

Another tip: disable firewall until you understand all the right rules.