Public bug reported: Hello,
This issue (Table 'neutron.ml2_vlan_allocations' doesn't exist") appears in the neutron.conf after a deploy in openstack-ansible. Our deploy is working fine, and I see no functional test issues, so this seems a low priority issue. This message appears on both trusty and Xenial. I guess this is a migration issue, and I don't know what we are doing wrong. Anyway, this is the log [1]. You can see in the same file the neutron release BUT this bug appeared in earlier releases. We just never paid attention because everything functionally works. Sadly, I cannot trace back further than what our gates store. I can tell you it's earlier than 2016-10-21 [2] (which is really old. SHA for the checked-out version is: 287bb35e167143388ab3d069af209341a75430f3). That also means the bug probably appeared in newton cycle. Any recent commit in neutron role will have these issues listed, so we can reproduce it quite easily with the latest sha's too. All the neutron logs available in our gates if you want. Best regards, JP. === [1]: http://logs.openstack.org/24/391524/48/check/gate-openstack- ansible-os_neutron-ansible-func-ubuntu- xenial/9c75e15/logs/openstack/openstack1/neutron/neutron- server.log.txt.gz#_2016-12-04_15_45_58_790 [2]: http://logs.openstack.org/05/389705/1/check/gate-openstack-ansible- os_neutron-ansible-func-ubuntu- xenial/b83b5e3/logs/openstack/openstack1/neutron/neutron- server.log.txt.gz#_2016-10-24_17_44_10_157 ** Affects: neutron Importance: Undecided Status: New ** Affects: openstack-ansible Importance: Undecided Status: New ** Also affects: openstack-ansible Importance: Undecided Status: New -- You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to neutron. https://bugs.launchpad.net/bugs/1648064 Title: Error "Table 'neutron.ml2_vlan_allocations' doesn't exist" in neutron.conf Status in neutron: New Status in openstack-ansible: New Bug description: Hello, This issue (Table 'neutron.ml2_vlan_allocations' doesn't exist") appears in the neutron.conf after a deploy in openstack-ansible. Our deploy is working fine, and I see no functional test issues, so this seems a low priority issue. This message appears on both trusty and Xenial. I guess this is a migration issue, and I don't know what we are doing wrong. Anyway, this is the log [1]. You can see in the same file the neutron release BUT this bug appeared in earlier releases. We just never paid attention because everything functionally works. Sadly, I cannot trace back further than what our gates store. I can tell you it's earlier than 2016-10-21 [2] (which is really old. SHA for the checked-out version is: 287bb35e167143388ab3d069af209341a75430f3). That also means the bug probably appeared in newton cycle. Any recent commit in neutron role will have these issues listed, so we can reproduce it quite easily with the latest sha's too. All the neutron logs available in our gates if you want. Best regards, JP. === [1]: http://logs.openstack.org/24/391524/48/check/gate-openstack- ansible-os_neutron-ansible-func-ubuntu- xenial/9c75e15/logs/openstack/openstack1/neutron/neutron- server.log.txt.gz#_2016-12-04_15_45_58_790 [2]: http://logs.openstack.org/05/389705/1/check/gate-openstack- ansible-os_neutron-ansible-func-ubuntu- xenial/b83b5e3/logs/openstack/openstack1/neutron/neutron- server.log.txt.gz#_2016-10-24_17_44_10_157 To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1648064/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : yahoo-eng-team@lists.launchpad.net Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
