Hi,
So actually these two are different issues:
1) https://review.openstack.org/#/c/61677 fixes the issue with a few
mandatory migrations not applying when ML2 plugin is used (the only
reason we hadn't seen it before is that those migrations were applied
on Jenkins CI nodes because LBaaS service p
Ok, I just did it.
https://bugs.launchpad.net/neutron/+bug/1260232
It seems that Yong found the same problem for ML2:
https://bugs.launchpad.net/bugs/1260224
I am just wondering, how come we did not catch this with ML2 when we are
claiming that it is our default plugin.
Edgar
On Wed, Dec 11,
Hi, Edgar,
Please file a bug on this. Obviously this was introduced by that commit.
Thanks,
Eugene.
On Thu, Dec 12, 2013 at 7:45 AM, Edgar Magana wrote:
> In commit:
> https://review.openstack.org/#/c/58814/
>
> There is an assumption that all "plugins" creates the
> plumgrid_neutron.agents w
Hi Edgar,
Nice catch! I proposed a fix here https://review.openstack.org/#/c/61663/
Could you please test it and and tell us if it fixes your problem?
Thanks,
Roman
On Thu, Dec 12, 2013 at 5:45 AM, Edgar Magana wrote:
> In commit:
> https://review.openstack.org/#/c/58814/
>
> There is an assum
In commit:
https://review.openstack.org/#/c/58814/
There is an assumption that all "plugins" creates the
plumgrid_neutron.agents which is not the case. I just tested big switch and
plumgrid and they are failing:
INFO [alembic.migration] Running upgrade havana -> e197124d4b9, add unique
constrain
