yahoo-eng-team team mailing list archive

[Luke Short <1904041@xxxxxxxxxxxxxxxxxx>]

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.

** Changed in: neutron
       Status: New => Invalid

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1904041

Title:
  Victoria neutron-db-sync fails with
  I38991de2b4_source_and_destination_ip_prefix_neutron_metering_rule.py

Status in neutron:
  Invalid

Bug description:
  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'

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1904041/+subscriptions