78bc33d300
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
OpenStack Neutron
Neutron is an OpenStack project to provide "network connectivity as a service" between interface devices (e.g., vNICs) managed by other OpenStack services (e.g., Nova).
To learn more about neutron:
- Documentation: https://docs.openstack.org/neutron/latest/
- Features: https://specs.openstack.org/openstack/neutron-specs
- Defects: https://launchpad.net/neutron
- Release notes: https://docs.openstack.org/releasenotes/neutron/index.html
- Source: https://opendev.org/openstack/neutron
If you would like to contribute to Neutron, please read the file CONTRIBUTING.rst or see the Neutron contributor guide:
https://docs.openstack.org/neutron/latest/contributor/contributing.html
Get in touch via email. Use [Neutron] in your subject.