OpenStack Snap

placement-mysql failed to bootstrap (blocks rest of deployment)

Bug #2033086 reported by Marian Gasparovic
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
OpenStack Snap
Triaged
High
Unassigned

Bug Description

Sunbeam bootstrap timed out because placement and nova units were still installing

https://oil-jenkins.canonical.com/artifacts/689796b7-96b2-4d4e-b052-b18badd1fde0/index.html

Revision history for this message
Marian Gasparovic (marosg) wrote :

Also keystone-mysql-router
https://oil-jenkins.canonical.com/artifacts/5ee0336c-d6a4-4e6c-8f55-0d956d2771c4/generated/generated/sunbeam/juju_status_openstack.txt

summary: - placement and nova charms not installed in time
+ Charms not installed in time during bootstrap
Revision history for this message
James Page (james-page) wrote : Re: Charms not installed in time during bootstrap

placement-mysql failed to bootstrap (see pod logs).

placement as a result is in a waiting state as the underlying mysql instance is not ready; nova is blocked as it tries to query the placement service on startup - its in the service catalog, but the service is not actually running.

Root cause is the failure to boostrap the placement-mysql instance.

Revision history for this message
James Page (james-page) wrote :
Changed in snap-openstack:
status: New → Triaged
importance: Undecided → High
summary: - Charms not installed in time during bootstrap
+ placement-mysql failed to bootstrap (blocks rest of deployment)
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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