The ceilometerdb-size validation passes with incorrect defaults

Bug #1643813 reported by Tomas Sedovic on 2016-11-22
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
tripleo
Medium
Katerina Pilatova

Bug Description

When remove any custom values for 'metering_time_to_live' or 'event_time_to_live' in /etc/ceilometer/ceilometer.conf, the validation will succeed even though the default values are "-1" which the validation should fail with.

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

Changed in tripleo:
assignee: nobody → Katerina Pilatova (kpilatov)
status: Triaged → In Progress

Reviewed: https://review.openstack.org/406076
Committed: https://git.openstack.org/cgit/openstack/tripleo-validations/commit/?id=63021890727c74147e5f1da2309d124eacac8724
Submitter: Jenkins
Branch: master

commit 63021890727c74147e5f1da2309d124eacac8724
Author: Katerina Pilatova <email address hidden>
Date: Fri Dec 2 12:32:55 2016 +0100

    ceilometerdb-size.yaml: Fix ceilometer database validation

    - now fails even if values are not set (they are -1 by default)
    - since the limit is infinite for all negative values, validation
      does not only check -1, but passes only for custom values >= 0

    Change-Id: I927e1b1296f3d89ac087916d8e4adc184185bcc5
    Closes-Bug: #1643813

Changed in tripleo:
status: In Progress → Fix Released

This issue was fixed in the openstack/tripleo-validations 5.3.0 release.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers