That error is showing that the tables Neutron wants to access aren't in the database it is accessing. Did you change databases during the reboot?
On Wed, 9 Mar 2016 at 13:39 Christopher Hull <chrishul...@gmail.com> wrote: > Ah Neutron didn't start... > I see this issue mentioned elsewhere, but haven't dug up a solution yet. > It was running before a reboot. Hmmm. > > neutron-server does not start: OperationalError: (OperationalError) no > such table: ml2_vlan_allocations > > > 2016-03-08 20:55:08.491 1664 ERROR neutron cursor.execute(statement, > parameters) > > 2016-03-08 20:55:08.491 1664 ERROR neutron OperationalError: > (sqlite3.OperationalError) no such table: ml2_vlan_allocations [SQL: > u'SELECT ml2_vlan_allocations.physical_network AS > ml2_vlan_allocations_physical_network, ml2_vlan_allocations.vlan_id AS > ml2_vlan_allocations_vlan_id, ml2_vlan_allocations.allocated AS > ml2_vlan_allocations_allocated \nFROM ml2_vlan_allocations'] > > 2016-03-08 20:55:08.491 1664 ERROR neutron > > > > _______________________________________________ > OpenStack-operators mailing list > OpenStack-operators@lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators > -- *Liam Haworth* | Junior Software Engineer | www.bluereef.com.au *_________________________________________________________________* *T*: +61 3 9898 8000 | *F*: +61 3 9898 8055
_______________________________________________ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
