OpenStack Keystone Charm

obsolete services and endpoints remain in OpenStack after upgrade

Bug #1881477 reported by James Troup
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
OpenStack Ceilometer Charm
Invalid
Medium
Unassigned
OpenStack Keystone Charm
Triaged
Medium
Unassigned

Bug Description

After upgrading a Xenial Ocata cloud up to Bionic Queens using the 19.10 charms, we find the following obsolete services and endpoints.

$ openstack service list | grep -i ceilometer
| fdd8dc2a7492403fa2723fbdb888c831 | ceilometer | metering |
$ openstack endpoint list | grep -i ceilometer
| 481316a277f74f4794aa8de29ce75db9 | regionOne | ceilometer | metering | True | internal | https://metering.example.com:8777 |
| 80db454e69c64e3b998326b9ddcc749c | regionOne | ceilometer | metering | True | public | https://metering.example.com:8777 |
| 9e2d42c480ae48f896392b839011b4f1 | regionOne | ceilometer | metering | True | admin | https://metering.example.com:8777 |
$

I think the charm should clean these up rather than requiring a human to do so.

Revision history for this message
Alex Kavanagh (ajkavanagh) wrote :

This is a keystone issue, so removing ceilometer charm and adding keystone charm.

Changed in charm-ceilometer:
importance: Undecided → Medium
status: New → Invalid
Revision history for this message
Alex Kavanagh (ajkavanagh) wrote :

Triaged; medium

Although desirable, this is potentially quite tricky to fix. The fix actually needs to be in keystone, which ought to 'know' what endpoints it has created for each relation it gets, and then when the get updated, remove the ones that aren't needed. Thus, I've added keystone to the bug. At the moment, the keystone charm doesn't cache (or otherwise mark) what came in on which relation and thus can't currently 'remove' the ones that it could as that information has been lost when the relation updates from ceilometer during the openstack upgrade.

Changed in charm-keystone:
importance: Undecided → Medium
status: New → Triaged
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.