<html><body>
<p><font size="2" face="sans-serif">My apologies, I didn't see that README. Looks like we need to explicitly call the migration as part of our upgrade path. Thanks for pointing that out!<br>
<br>
</font><br>
<br>
<tt><font size="2">Itzik Brown <itzikb@dev.mellanox.co.il> wrote on 04/08/2014 04:06:32 PM:<br>
<br>
> From: Itzik Brown <itzikb@dev.mellanox.co.il></font></tt><br>
<tt><font size="2">> To: "OpenStack Development Mailing List (not for usage questions)" <br>
> <openstack-dev@lists.openstack.org>, </font></tt><br>
<tt><font size="2">> Date: 04/08/2014 04:11 PM</font></tt><br>
<tt><font size="2">> Subject: Re: [openstack-dev] [neutron] alembic migration not <br>
> working? specifically in regards to ml2_port_bindings table</font></tt><br>
<tt><font size="2">> <br>
> Hi,<br>
> Have you looked at <a href="https://github.com/openstack/neutron/blob/master/">https://github.com/openstack/neutron/blob/master/</a><br>
> neutron/db/migration/README ?<br>
> <br>
> Itzik<br>
</font></tt><br>
<tt><font size="2">> On 08/04/2014 23:41, Paul Ward wrote:</font></tt><br>
<tt><font size="2">> Is anyone else out there seeing failures that appear to be because <br>
> alembic is not upgrading db tables in neutron? I'm seeing, on an <br>
> upgrade, that ml2_port_bindings is not being updated to remove <br>
> column cap_port_filter or add columns vnic_type, profile, or <br>
> vif_details, I'm also seeing the subnets table not getting updated <br>
> with the ipv6_ra_mode column.<br>
> <br>
> I'm not intimately familiar with alembic so I'm not really sure what<br>
> is supposed to kick off the upgrade/downgrade or if the following <br>
> revision chains are ok. Does merely starting neutron-server <br>
> initiate the upgrade? In perusing some of the ml2_port_bindings <br>
> alembic files, I came up with these revision chains:<br>
> <br>
> 32a65f71af51 (where ml2_port_bindings was first created)<br>
> ^<br>
> 14f24494ca31 (this is creating some arista tables... I don't know <br>
> why it's a down_revision for ml2_port_bindings table creation above)<br>
> <br>
> <br>
> <br>
> 157a5d299379 (adds profile column to ml2_port_bindings table.... <br>
> apparently not called in my environment's upgrade)<br>
> ^<br>
> 50d5ba354c23 (adds vif_details column to ml2_port_bindings table <br>
> and removes cap_port_filter colume from ml2_port_bindings table.... <br>
> apparently not called in my environment's upgrade)<br>
> ^<br>
> 27cc183af192 (first file to add a column, vnic_type, to <br>
> ml2_port_bindings.... apparently not called in my environment's upgrade)<br>
> ^<br>
> 4ca36cfc898c (creates table neutron_nsx_router_mappings... don't <br>
> see how this is related to ml2_port_bindings other than similar <br>
> foreign key constraints)<br>
> <br>
> Notice the chains do not connect with each other. It seems to me <br>
> that 27cc183af192 should actually call out 32a65f71af51 as the <br>
> down_revision as 32a65f71af51 is where the ml2_port_bindings table <br>
> was first created. 4ca36cfc898c just deals with the <br>
> neutron_nsx_router_mappings table... I don't see how that's related <br>
> to ml2_port_bindings table other than having some similar foreign <br>
> key constraints.<br>
> <br>
> Thanks in advance! </font></tt><br>
<tt><font size="2">> <br>
> _______________________________________________<br>
> OpenStack-dev mailing list<br>
> OpenStack-dev@lists.openstack.org<br>
> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
</font></tt><br>
<tt><font size="2">> _______________________________________________<br>
> OpenStack-dev mailing list<br>
> OpenStack-dev@lists.openstack.org<br>
> <a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
</font></tt></body></html>