> "Can't DROP COLUMN `vm_state`; check that it exists") [SQL: ALTER TABLE build_requests DROP COLUMN vm_state]
As far as I see this is a bug in the DB migration code introduced in yoga: https://review.opendev.org/c/openstack/nova/+/812145/2/nova/db/api/migrations/versions/b30f573d3377_remove_unused_build_requests_columns.py#31
This tries to drop the vm_state from the build_requests. But vm_state column only exists there if the DB schema was created in older than Newton nova version as after the commit https://review.opendev.org/c/openstack/nova/+/305953/10/nova/db/sqlalchemy/api_models.py#174 (merged in Newton) the column is not added to the table any more.
> "Can't DROP COLUMN `vm_state`; check that it exists")
[SQL: ALTER TABLE build_requests DROP COLUMN vm_state]
As far as I see this is a bug in the DB migration code introduced in yoga: https:/ /review. opendev. org/c/openstack /nova/+ /812145/ 2/nova/ db/api/ migrations/ versions/ b30f573d3377_ remove_ unused_ build_requests_ columns. py#31
This tries to drop the vm_state from the build_requests. But vm_state column only exists there if the DB schema was created in older than Newton nova version as after the commit https:/ /review. opendev. org/c/openstack /nova/+ /305953/ 10/nova/ db/sqlalchemy/ api_models. py#174 (merged in Newton) the column is not added to the table any more.