Victoria neutron-db-sync fails with I38991de2b4_source_and_destination_ip_prefix_neutron_metering_rule.py

[Luke Short]

Both new deployments and upgrades of OpenStack fail when running the neutron_db_sync command. This is seen when using the Victoria release of Neutron. This has been experienced in both the Kolla-Ansible and TripleO communities.

Here are the relevant errors:
- Kolla-Ansible = https://www.reddit.com/r/openstack/comments/jqi7sx/kolla_fails_to_upgrade_neutron_database/
- TripleO = http://paste.openstack.org/show/799965/

This is the main error:
2020-11-12T00:20:15.810555929+00:00 stderr F alembic.script.revision.ResolutionError: No such revision or branch 'I38991de2b4'

[Rodolfo Alonso (rodolfo-alonso-hernandez)]

Hello:

I've been testing the upgrade procedure from previous versions to Victoria milestone, that is revision I38991de2b4. When I execute the upgrade command, this is what I get:

stack@dev20:/opt/stack$ neutron-db-manage upgrade --expand
INFO [alembic.runtime.migration] Context impl MySQLImpl.
INFO [alembic.runtime.migration] Will assume non-transactional DDL.
  Running upgrade (expand) for neutron ...
INFO [alembic.runtime.migration] Context impl MySQLImpl.
INFO [alembic.runtime.migration] Will assume non-transactional DDL.
INFO [alembic.runtime.migration] Running upgrade 49d8622c5221 -> I38991de2b4
  OK

Can you confirm that the code you have downloaded has this revision? Are you in stable/victoria branch? Is it possible to see the previous log lines (if you are deploying a new system, something like [1])?

Regards.

[1]http://paste.openstack.org/show/800049/

[Luke Short (ekultails)]

I did some further digging and found that TripleO was pulling Neutron packages from master. I updated/synced to the latest development build ("current" RDO packages) of Victoria and now TripleO is using the correct packages. neutron-db-sync now works as expected. I cannot speak for the Kolla-Ansible side of the house but I suspect it may have been a similar problem.

Side note: TripleO used to use Kolla images but in Victoria and newer we have switched to our own containers to keep dependencies down and increase build time.