dashboard workload state is 'ready' even though db relation is needed to work with keystone v3
Bug #1680602 reported by
Ryan Beisner
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Dashboard Charm |
Triaged
|
Low
|
Unassigned | ||
Openstack Mojo Testing |
Triaged
|
Medium
|
Unassigned |
Bug Description
The openstack-dashboard charm must have a database relation when keystone V3 is in use. But, the charm's required relations do not represent that. This causes the workload state to declare Ready when in fact the dashboard is likely not ready and usable.
As reference, the openstack-dashboard readme says:
"Keystone V3
If the charm is being deployed into a keystone v3 enabled environment then the charm needs to be related to a database to store session information. This is only supported for Mitaka or later."
The charm should be adjusted to expect a db relation when using ksv3.
The mojo-openstack spec ksv3 bundles should also be updated to include the relation.
summary: |
- workload state is 'ready' even though db relation is needed to work with - keystone v3 + dashboard workload state is 'ready' even though db relation is needed to + work with keystone v3 |
Changed in charm-openstack-dashboard: | |
milestone: | 18.02 → 18.05 |
Changed in charm-openstack-dashboard: | |
milestone: | 18.05 → 18.08 |
Changed in charm-openstack-dashboard: | |
milestone: | 18.08 → 18.11 |
Changed in charm-openstack-dashboard: | |
milestone: | 18.11 → 19.04 |
Changed in charm-openstack-dashboard: | |
milestone: | 19.04 → 19.07 |
Changed in charm-openstack-dashboard: | |
assignee: | James Page (james-page) → nobody |
Changed in charm-openstack-dashboard: | |
milestone: | 19.07 → 19.10 |
Changed in charm-openstack-dashboard: | |
milestone: | 19.10 → 20.01 |
Changed in charm-openstack-dashboard: | |
milestone: | 20.01 → 20.05 |
Changed in charm-openstack-dashboard: | |
milestone: | 20.05 → 20.08 |
Changed in charm-openstack-dashboard: | |
milestone: | 20.08 → none |
To post a comment you must log in.
As this is a usability issue, Triaging as Low.