<html><body>
<p><font size="2" face="sans-serif">Is anyone else out there seeing failures that appear to be because alembic is not upgrading db tables in neutron? I'm seeing, on an upgrade, that ml2_port_bindings is not being updated to remove column cap_port_filter or add columns vnic_type, profile, or vif_details, I'm also seeing the subnets table not getting updated with the ipv6_ra_mode column.</font><br>
<br>
<font size="2" face="sans-serif">I'm not intimately familiar with alembic so I'm not really sure what is supposed to kick off the upgrade/downgrade or if the following revision chains are ok. Does merely starting neutron-server initiate the upgrade? In perusing some of the ml2_port_bindings alembic files, I came up with these revision chains:</font><br>
<br>
<font size="2" face="sans-serif">32a65f71af51 (where ml2_port_bindings was first created)</font><br>
<font size="2" face="sans-serif">^</font><br>
<font size="2" face="sans-serif">14f24494ca31 (this is creating some arista tables... I don't know why it's a down_revision for ml2_port_bindings table creation above)</font><br>
<br>
<br>
<br>
<font size="2" face="sans-serif">157a5d299379 (adds profile column to ml2_port_bindings table.... apparently not called in my environment's upgrade)</font><br>
<font size="2" face="sans-serif">^</font><br>
<font size="2" face="sans-serif">50d5ba354c23 (adds vif_details column to ml2_port_bindings table and removes cap_port_filter colume from ml2_port_bindings table.... apparently not called in my environment's upgrade)</font><br>
<font size="2" face="sans-serif">^</font><br>
<font size="2" face="sans-serif">27cc183af192 (first file to add a column, vnic_type, to ml2_port_bindings.... apparently not called in my environment's upgrade)</font><br>
<font size="2" face="sans-serif">^</font><br>
<font size="2" face="sans-serif">4ca36cfc898c (creates table neutron_nsx_router_mappings... don't see how this is related to ml2_port_bindings other than similar foreign key constraints)</font><br>
<br>
<font size="2" face="sans-serif">Notice the chains do not connect with each other. It seems to me that 27cc183af192 should actually call out 32a65f71af51 as the down_revision as 32a65f71af51 is where the ml2_port_bindings table was first created. 4ca36cfc898c just deals with the neutron_nsx_router_mappings table... I don't see how that's related to ml2_port_bindings table other than having some similar foreign key constraints.</font><br>
<br>
<font size="2" face="sans-serif">Thanks in advance!</font></body></html>