959da8cd03
At the moment Cloudkitty is targeted at all LXC hosts along with containers which is not needed nor intended. Unfortunatelly there's no really good compatible fix exist, so action from operator is required to handle transition to new naming for the service. Change-Id: I9360495e3b3347568969e36e0e96bb1325efd59f
18 lines
757 B
YAML
18 lines
757 B
YAML
---
|
|
|
|
upgrade:
|
|
- |
|
|
Ensure that in openstack_user_config.yml / conf.d ``cloudkitty_hosts`` are
|
|
replaced with ``rating_hosts``.
|
|
For deployments with LXC containers: after upgrade is completed make sure
|
|
that Cloudkitty is not running on your LXC hosts anymore, after which you
|
|
should be able to remove LXC hosts from cloudkitty_all group in inventory.
|
|
|
|
fixes:
|
|
- |
|
|
Due to issue in env.d defenition for Cloudkitty, service was installed not
|
|
only inside LXC containers, but also to all LXC hosts, which was not
|
|
intended. This was fixed in env.d definition for the service, and it
|
|
was renamed from ``cloudkitty_hosts`` to ``rating_hosts``, which should be
|
|
reflected in your ``openstack_user_config.yml`` or conf.d files.
|