This DB migration seems to be quite old (credit to tkajinam++)
Seems odd to be trying to do this migration that was included 4 years ago. The created_at column clearly exists in the table. Checking the versions of openstack-neutron and the container versions, everything seems to be at the latest available:
╰─ grep neutron installed-rpms
openstack-neutron-12.1.1-18.el7ost.noarch Wed Sep 16 18:35:53 2020
Which is the latest available:
There seems to be a conflict somewhere here. We'll keep digging to see where the older Revision ID is coming from.
Are we able to get the output from the following on one of the controllers?
docker exec -it neutron_api neutron-db-manage current --verbose
[root@overcloud-controller-0 ~]# sudo su -
[root@overcloud-controller-0 ~]# docker exec -it neutron_api neutron-db-manage current --verbose
python-networking-vmware-nsx is installed by default laying down files in /usr/lib/python2.7/site-packages/vmware_nsx
I'm working on rebuilding the tables to aede17d51d0f for import, then we can force set the alembic version to match.
Fixed on customer site cleaning the (unused anyway) tables and recreating them to proper state before attempting update again, which succeeded