Sunbeam configure fails if not bootstrapped
Bug #2024996 reported by
Billy Olsen
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| OpenStack Snap |
Fix Released
|
High
|
Liam Young | ||
Bug Description
As reported in Bug #2024992, when the `sunbeam configure ...` command is run when the bootstrap does not succeed for fails, the user is met with an ugly error message that doesn't help the user understand what's going on.
The configure command should check to see if the cluster is bootstrapped prior to starting so that the user can get a more friendly user message instead of something like:
An unexpected error has occurred. Please run 'sunbeam inspect' to generate an inspection report.
Error: Leader for application 'keystone' is missing from model 'openstack'
| Changed in snap-openstack: | |
| status: | New → Triaged |
| importance: | Undecided → High |
| Changed in snap-openstack: | |
| assignee: | nobody → Liam Young (gnuoy) |
Revision history for this message
| Guillaume Boutry (gboutry) wrote | #1 |
| Changed in snap-openstack: | |
| status: | Triaged → Fix Committed |
| Changed in snap-openstack: | |
| status: | Fix Committed → Won't Fix |
| status: | Won't Fix → Fix Committed |
| Changed in snap-openstack: | |
| status: | Fix Committed → Fix Released |
| Changed in snap-openstack: | |
| milestone: | none → 2023.1.2 |
To post a comment you must log in.
Fix committed as part of https:/