hardcoded timeout Error: Timed out while waiting for model 'openstack' to be ready

Bug #2065469 reported by Nobuto Murata
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
OpenStack Snap
Triaged
Wishlist
Unassigned

Bug Description

It looks like the deployment timeout is hardcoded as OPENSTACK_DEPLOY_TIMEOUT=5400 (90min) and there is no way to extend it for environments where the internet connection is not fast enough to fetch all resources such as container images.

$ sunbeam cluster bootstrap --role control --role compute --role storage
Use proxy to access external network resources? [y/n] (n):
Management networks shared by hosts (CIDRs, separated by comma) (192.168.123.0/24):
MetalLB address allocation range (supports multiple ranges, comma separated) (192.168.123.81-192.168.123.90):
Disks to attach to MicroCeph (comma separated list) (/dev/sdc): /dev/vdc
⠇ Deploying OpenStack Control Plane to Kubernetes (this may take a while) ... waiting for services to come online (23/25)Timed out while waiting for model 'openstack' to be ready
Error: Timed out while waiting for model 'openstack' to be ready

Nobuto Murata (nobuto)
description: updated
Revision history for this message
James Page (james-page) wrote :

We have relied mainly on the idempotency of re-running a command to deal with this situation.

Being able to override this for a more expert user with experience on timing expectations for a specific deployment is probably useful.

Changed in snap-openstack:
status: New → Triaged
importance: Undecided → Wishlist
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.