Once you get it configured with a normal db backend, you will have to run the neutron-db-manage command again to repopulate the schema. On Mar 8, 2016 18:43, "Kevin Benton" <ke...@benton.pub> wrote:
> Ah, it looks like neutron isn't configured to use a database so it's > defaulting to an in-memory sqlite server. Check your connection string in > the neutron config. > On Mar 8, 2016 18: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 >> >>
_______________________________________________ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
