Deferred delete tests might fail if periodic cleanup task runs

[Hans Lindgren]

All deferred delete tests set reclaim_instance_interval to 1. This is fine for the test_deferred_delete test that depends on the periodic task _reclaim_queued_deletes to run.

For the other tests however, in the unlikely event that the periodic task do run before the tests are done, it will interfere with the tests by terminating the instance in the middle of it.

An example of this can be seen here: http://logs.openstack.org/23376/3/gate/gate-nova-python26/18069/console.html.gz

By setting the interval longer than the actual test run, this can be avoided.

[OpenStack Infra (hudson-openstack)]

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

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/23528
Committed: http://github.com/openstack/nova/commit/f98012174005faa4a88cb694ee900396f50f0f75
Submitter: Jenkins
Branch: master

commit f98012174005faa4a88cb694ee900396f50f0f75
Author: Hans Lindgren <email address hidden>
Date: Tue Mar 5 11:02:46 2013 +0100

    Adjusts reclaim instance interval of deferred delete tests

    All deferred delete tests set reclaim_instance_interval to 1. This is
    fine for the test_deferred_delete test that depends on the periodic
    task _reclaim_queued_deletes to run.

    For the other tests however, in the unlikely event that the periodic
    task do run before the tests are done, it will interfere with the tests
    by terminating the instance in the middle of it.

    By setting the interval longer than the actual test run, this can be
    avoided.

    Resolves bug 1146510.

    Change-Id: I606cd9f3277cc86cf4f9811da2a10efc7433b9d0