Comment 27 for bug 1983053

Reviewed: https://review.opendev.org/c/openstack/neutron/+/893097
Committed: https://opendev.org/openstack/neutron/commit/78bc33d300dc268d193fd2a895ed26079d441c3d
Submitter: "Zuul (22348)"
Branch: master

commit 78bc33d300dc268d193fd2a895ed26079d441c3d
Author: Slawek Kaplonski <email address hidden>
Date: Tue Aug 29 19:50:33 2023 +0200

    [Fullstack] Use new DB for each running test

    Until now neutron fullstack tests which were run by the same worker were
    using same DB but after test content of the DB was cleaned.
    This could cause problems e.g. for default security group rules which
    weren't created properly in second test run by the same worker.

    To fix that issue patch [1] was proposed and merged some time ago. But
    this didn't solve the problem so this patch is effectively reverting [1]
    and proposing another solution which will make each fullstack test to
    use own DB and run db migration script.

    As running DB migration before every test makes this jobs to run a bit
    longer than it took before, this patch also increases timeout for the
    fullstack job(s) to 3h (10800 seconds).

    [1] https://review.opendev.org/c/openstack/neutron/+/891040

    Related-bug: #1983053
    Change-Id: Ia261b4c62db9a99ef6eb161acb4609520e45d101