`cluster bootstrap` fails - timeout reached
Bug #2033116 reported by
Peter Matulis
This bug affects 3 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| OpenStack Snap |
New
|
Undecided
|
Unassigned | ||
Bug Description
I just hit this, and I've seen several reports in the wild about the same problem. I'm deploying a single-node scenario and my machine has plenty of resources (Icarus metal: 'node-mees') yet I'm encountering a hardcoded timeout.
$ sudo snap install --channel 3.2/stable juju
$ sudo snap install --channel 2023.1/edge openstack
$ sunbeam prepare-node-script | bash -x && newgrp snap_daemon
$ sunbeam cluster bootstrap --accept-defaults
⠇ Deploying OpenStack Control Plane to Kubernetes (this may take a while) ... waiting for services to come online (0/29)Timed out while waiting for model 'opens
tack' to be ready
Error: Timed out while waiting for model 'openstack' to be ready
Revision history for this message
| Peter Matulis (petermatulis) wrote | #1 |
Revision history for this message
| James Page (james-page) wrote | #2 |
To post a comment you must log in.
As we discussed I think you're probably hitting the Dockerhub rate limits (I use the same lab and hit this sometimes as well).
This is a general issue with where microk8s and Juju source container images from - discussing with these teams to see if we can improve this situation.