Red Hat Bugzilla – Bug 1284047
ceilometer rpc_backed is deprecated
Last modified: 2016-12-14 10:18:29 EST
Description of problem:
On a director deployed ceilometer, we have
this has been deprecated (and removed in liberty), the correct value is
This must be changed in OSP-8 and ideally before (to simplify upgrades)
It has been fixed upstream in the ceilometer puppet module
Version-Release number of selected component (if applicable):
@Derek: I don't understand the problem.
https://review.openstack.org/#/c/196036/ is in OPM (at least for OSP8, Liberty). You want a backport to OSP7 (Kilo) ?
@Emilien ideally it would be backported to OSP7, the upgrade process involves the package being upgraded and the services being restarted before the new puppet modules get applied. To avoid an error before the new puppet modules are applied we would need the updated value in OSP7.
Alternatively this can be worked around as part of the upgrade process, so I wouldn't call it a blocker by any means.
Jirka, are you handling this already? or do we need to track it?
We're handling this. Derek set the value via crudini:
This bug did not make the OSP 8.0 release. It is being deferred to OSP 10.
Still valid issue:
$ rpm -qa | grep openstack-tripleo-heat-templates
# grep ^rpc_backend /etc/ceilometer/ceilometer.conf
The puppet stuff itself looks good, but:
This is the culprit https://github.com/openstack/tripleo-heat-templates/blob/master/extraconfig/tasks/major_upgrade_controller_pacemaker_1.sh#L181
(In reply to Mehdi ABAAKOUK from comment #12)
> # grep ^rpc_backend /etc/ceilometer/ceilometer.conf
I think that's the correct value though (see comment #0), so should this BZ be marked 'verified' rather? The BZ was breaking update from 7 to 8, and has been fixed back then, otherwise we couldn't update Ceilometer to OSP 8 correctly IIRC.
Oh yeah sorry I have misreading, so yeah everything is OK.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.