charm should make it more obvious that gnocchi is not yet initialised
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Ceilometer Charm |
Fix Released
|
Medium
|
Unassigned |
Bug Description
It is currently mandatory to manually run the ceilometer-upgrade action post deployment in order for gnocchi to be populated with ceilometer resources (and be able to do anything). The actions.yaml does say "This action must be run post deployment when ceilometer is related to gnocchi" but that's only useful if you think to look there. Perhaps it would be better to do one or more of the following:
* set a charm status saying that gnocchi is not ready yet until this action has been run
* have the charm automatically run the upgrade (using goal state info to know when gnocchi is ready)
* rename the action to something like "init-gnocchi" so that it sound less like something that needs to be run only when upgrading to gnocchi from mongo.
tags: | added: sts |
Changed in charm-ceilometer: | |
assignee: | nobody → David Ames (thedac) |
Changed in charm-ceilometer: | |
assignee: | nobody → David Ames (thedac) |
Changed in charm-ceilometer: | |
milestone: | 19.04 → 19.07 |
Changed in charm-ceilometer: | |
milestone: | 19.07 → 19.10 |
Changed in charm-ceilometer: | |
milestone: | 19.10 → 20.01 |
Changed in charm-ceilometer: | |
milestone: | 20.01 → 20.05 |
Changed in charm-ceilometer: | |
milestone: | 20.05 → 20.08 |
Changed in charm-ceilometer: | |
milestone: | 20.08 → none |
Triage:
First set ceilometer workload status blocked if the ceilometer-upgrade action has not run.
Secondly, explore goal state on both gnocchi and ceilometer to revisit automatically running the upgrade code path.