We would like to drop a few columns from the Models class and subsequently identify these fields for a database removal in the next openstack ('M') release.
However In nova/tests/unit/db/test_migrations.py - there's a test that does a check between the DB schema and models.py called "test_models_sync" - that matches the models and the db schema to ensure that there's no difference between the two.
We would like to have a 'whitelist' of attributes that are identified for cleanups from the models.py that could act as a constraint while doing this models_sync test. The attributes could be called "allow_missing_from_model" or "allow_missing_from_db" that would help us get past this error in the tests and at the same time help us maintain a list of attributes - that needs cleanup from the DB in the future releases.
The test failure could be observed on this review: https://review.openstack.org/#/c/192760/
Here's the error trace for the UT that fails:
2015-06-24 18:29:04.042 |
2015-06-24 18:29:04.042 | Captured traceback:
2015-06-24 18:29:04.042 | ~~~~~~~~~~~~~~~~~~~
2015-06-24 18:29:04.042 | Traceback (most recent call last):
2015-06-24 18:29:04.042 | File "/home/
2015-06-24 18:29:04.042 | "Models and migration scripts aren't in sync:\n%s" % msg)
2015-06-24 18:29:04.042 | File "/home/
2015-06-24 18:29:04.042 | raise self.failureExc
2015-06-24 18:29:04.042 | AssertionError: Models and migration scripts aren't in sync:
2015-06-24 18:29:04.042 | [ ( 'remove_column',
2015-06-24 18:29:04.043 | None,
2015-06-24 18:29:04.043 | 'instances',
2015-06-24 18:29:04.043 | Column(
2015-06-24 18:29:04.043 |