Since tests run in parallel, cfg.CONF state can be not that we expect

[Mehdi Abaakouk]

Hi,

After investigation of why this merge failed:
http://logs.openstack.org/10/39510/4/check/gate-ceilometer-python27/ed09521/console.html

I have discovered that tests randomly failed when mongo < 2.2 is installed
$ for i in $(seq 0 20) ; do tox -epy27 >/dev/null 2>&1 && echo -n . || echo -n X ; done
....X..XXX..X..X.X.X.

After investigation, all tests in tests.collector.dispatcher.test_db assume that the cfg.CONF.database.connection is the default one (ie: a sqlite databases) or sometimes it is a other backends.

because when a test is skipped, the cfg.CONF is not reset

Cheers

[OpenStack Infra (hudson-openstack)]

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

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/41422
Committed: http://github.com/openstack/ceilometer/commit/cc803b10f65fa71336be3c4184726a97d2713d8c
Submitter: Jenkins
Branch: master

commit cc803b10f65fa71336be3c4184726a97d2713d8c
Author: Mehdi Abaakouk <email address hidden>
Date: Mon Aug 12 14:31:55 2013 +0200

    Use new olso fixture in CM tests

    Before this change mox and cfg.CONF wasn't cleaned up correctly if
    skipTest is called, because when skipTest is used teardown is not
    called.

    Now we use the oslo fixtures to setup oslo.config and mox to ensure the
    cleanup is done between each tests.

    Fixes bug #1211239

    Change-Id: I5075c99106742859f0705b765f8ed4aa9be494d7