ceilometer-dbsync shouldn't still create alarm tables

Bug #1578128 reported by Liusheng on 2016-05-04
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Ceilometer
Undecided
Liusheng

Bug Description

since we have remove alarm out of ceilometer code tree, but if wen run ceilometer-dbsync, the alarm tables will still be created, we need to add migration script to remove the alarm tables.

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

Changed in ceilometer:
assignee: nobody → Liusheng (liusheng)
status: New → In Progress

Reviewed: https://review.openstack.org/312399
Committed: https://git.openstack.org/cgit/openstack/ceilometer/commit/?id=800034dc0bbb9502893dedd9bcde7c170780c375
Submitter: Jenkins
Branch: master

commit 800034dc0bbb9502893dedd9bcde7c170780c375
Author: liusheng <email address hidden>
Date: Wed May 4 17:18:49 2016 +0800

    Add a tool to clean the legacy alarm tables

    Since we have moved alarm out of ceilometer, when run ceilometer-dbsync,
    the alarm tables will still be created and won't be removed. This change
    added a tool that allow users to drop the legacy alarm and alarm_history
    tables with SQL backends.

    Change-Id: Ia831741319fd8e198f54a7d4a99b4d7833074e8e
    Closes-Bug: #1578128
    Signed-off-by: liusheng <email address hidden>

Changed in ceilometer:
status: In Progress → Fix Released

This issue was fixed in the openstack/ceilometer 7.0.0.0b2 development milestone.

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

Other bug subscribers