Hi Robert, all,
But what are we meant to do? Nova etc are dead easy: nova-manage db sync
every time the code changes, done.
I believe, it's not different from Nova: run db sync every time the
code changes. It's the only way to guarantee the most recent DB schema
version is used.
So we had this bug earlier in the week;
https://bugs.launchpad.net/tripleo/+bug/1283921
Table 'ovs_neutron.ml2_vlan_allocations' doesn't exist in neutron-server.log
We fixed this by running neutron-db-migrate upgrade head... which we
figured out by googling and asking weird questions in
