Neutron functional tests can't target both postgres and mysql in the same test run
Bug #1372981 reported by
Ann Taraday
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
devstack |
Invalid
|
Undecided
|
Henry Gessau | ||
neutron |
Fix Released
|
Medium
|
Mark McClain |
Bug Description
Devstack can't install both postgres and mysql in a given run, which prevents the Neutron functional test suite from validating db migrations against both dbs in the same run.
Once devstack support for installing both db servers has been added, the migration tests can be moved from the unittest suite (where the openstack_citest credentials are available by default) to the functional job.
Changed in python-neutronclient: | |
assignee: | nobody → Ann Kamyshnikova (akamyshnikova) |
Changed in python-neutronclient: | |
importance: | Undecided → Medium |
affects: | python-neutronclient → neutron |
Changed in neutron: | |
status: | New → Confirmed |
summary: |
- ModelsMigrationsSync test should be moved to functional tests + Neutron db migration tests can't run via the functional job |
summary: |
- Neutron db migration tests can't run via the functional job + Only one of (postgres, mysql) can be installed by devstack |
summary: |
- Only one of (postgres, mysql) can be installed by devstack + Only one of (postgres, mysql) can be installed by devstack at a time |
summary: |
- Only one of (postgres, mysql) can be installed by devstack at a time + Neutron functional tests need to be able to target both postgres and + mysql in the same test run |
summary: |
- Neutron functional tests need to be able to target both postgres and - mysql in the same test run + Neutron functional tests can't target both postgres and mysql in the + same test run |
description: | updated |
Changed in devstack: | |
assignee: | nobody → Henry Gessau (gessau) |
status: | New → Confirmed |
Changed in neutron: | |
assignee: | Ann Kamyshnikova (akamyshnikova) → Henry Gessau (gessau) |
status: | Confirmed → In Progress |
Changed in neutron: | |
assignee: | Henry Gessau (gessau) → Rossella Sblendido (rossella-o) |
Changed in neutron: | |
assignee: | Rossella Sblendido (rossella-o) → Henry Gessau (gessau) |
Changed in neutron: | |
assignee: | Henry Gessau (gessau) → Rossella Sblendido (rossella-o) |
Changed in neutron: | |
assignee: | Rossella Sblendido (rossella-o) → Henry Gessau (gessau) |
Changed in neutron: | |
assignee: | Henry Gessau (gessau) → Mark McClain (markmcclain) |
Changed in neutron: | |
milestone: | none → kilo-2 |
status: | Fix Committed → Fix Released |
Changed in neutron: | |
milestone: | kilo-2 → 2015.1.0 |
To post a comment you must log in.
So I'm not sure I understand the reason for wanting to move the migration tests there. Sure there is the consistency aspect where the migration tests are actually functional tests but aside from that what is the reason for wanting to do this?
Especially since neutron has a separate functional test suite that requires devstack it feels like the migration tests should remain independent of that, since they only require a running db. I can see why putting them in the unit test namespace could be confusing, and if that is the only reason for moving them maybe just put them in a separate place which is different.