mongodb parameter is dropped in Mitaka

Bug #1528612 reported by Emilien Macchi
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
puppet-ceilometer
Fix Released
Critical
Emilien Macchi
tripleo
Expired
Undecided
Unassigned

Bug Description

See:
https://github.com/openstack/ceilometer/commit/a6d608a33235dfa0d4ef91e3a3d69359ceb0263f

An option has been dropped in Mitaka, so we need to update the module.
Until then, puppet-ceilometer is broken on Mitaka when running MongoDB.

Changed in puppet-ceilometer:
assignee: nobody → Emilien Macchi (emilienm)
importance: Undecided → Critical
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to puppet-ceilometer (master)

Fix proposed to branch: master
Review: https://review.openstack.org/260604

Changed in puppet-ceilometer:
status: New → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to puppet-ceilometer (master)

Reviewed: https://review.openstack.org/260604
Committed: https://git.openstack.org/cgit/openstack/puppet-ceilometer/commit/?id=51fdead1dcd257314af1ae4941557221f7150aa5
Submitter: Jenkins
Branch: master

commit 51fdead1dcd257314af1ae4941557221f7150aa5
Author: Emilien Macchi <email address hidden>
Date: Tue Dec 22 16:41:03 2015 +0100

    deprecate mongodb_replica_set parameter

    mongodb_replica_set parameter has been dropped in Mitaka [1] and has no
    effect anymore.
    This patch deprecated our interface by sending a warning if the param is
    set. If set, it has no effect though, since the param does not exist
    anymore upstream.

    [1] https://github.com/openstack/ceilometer/commit/a6d608a33235dfa0d4ef91e3a3d69359ceb0263f

    Closes-Bug: #1528612
    Change-Id: I49123b0f1353e24b217ea6f16f556ab25a6c86b0

Changed in puppet-ceilometer:
status: In Progress → Fix Released
Revision history for this message
Emilien Macchi (emilienm) wrote : Cleanup EOL bug report

This is an automated cleanup. This bug report has been closed because it
is older than 18 months and there is no open code change to fix this.
After this time it is unlikely that the circumstances which lead to
the observed issue can be reproduced.

If you can reproduce the bug, please:
* reopen the bug report (set to status "New")
* AND add the detailed steps to reproduce the issue (if applicable)
* AND leave a comment "CONFIRMED FOR: <RELEASE_NAME>"
  Only still supported release names are valid (LIBERTY, MITAKA, NEWTON, OCATA, PIKE, PIKE).
  Valid example: CONFIRMED FOR: LIBERTY

Changed in tripleo:
status: New → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.