[Openstack-operators] Neutron doesn't start - was Neutron connection issue
Christopher Hull
chrishull42 at gmail.com
Wed Mar 9 02:55:17 UTC 2016
Oh. My bad.
I installed Neutron Controller and Compute on the same node. When I did
Compute, I commented out the DB connection (as it said)... OOPS! Put it
back. Now it works. I feel silly.
NOW
I'm wondering where my Neutron Compute agent is. I should see one Compute
in this list.
neutron agent-list
+--------------------------------------+--------------------+--------+-------+----------------+---------------------------+
| id | agent_type | host |
alive | admin_state_up | binary |
+--------------------------------------+--------------------+--------+-------+----------------+---------------------------+
| 41974f0e-4342-4027-a771-53443a8d1911 | Metadata agent | maersk |
:-) | True | neutron-metadata-agent |
| 9f002230-33ea-4523-a736-8d96a96a85f1 | Linux bridge agent | maersk |
:-) | True | neutron-linuxbridge-agent |
| ccb8cd1c-6c47-4df9-9e87-4b3b651c3427 | L3 agent | maersk |
:-) | True | neutron-l3-agent |
| ef5611be-edf3-4565-aaa7-a833bdc79d57 | DHCP agent | maersk |
:-) | True | neutron-dhcp-agent |
+--------------------------------------+--------------------+--------+-------+----------------+---------------------------+
I should see this.
neutron agent-list+--------------------------------------+--------------------+------------+-------+----------------+---------------------------+|
id | agent_type | host
| alive | admin_state_up | binary
|+--------------------------------------+--------------------+------------+-------+----------------+---------------------------+|
08905043-5010-4b87-bba5-aedb1956e27a | Linux bridge agent | compute1
| :-) | True | neutron-linuxbridge-agent ||
27eee952-a748-467b-bf71-941e89846a92 | Linux bridge agent | controller
| :-) | True | neutron-linuxbridge-agent ||
830344ff-dc36-4956-84f4-067af667a0dc | L3 agent | controller
| :-) | True | neutron-l3-agent ||
dd3644c9-1a3a-435a-9282-eb306b4b0391 | DHCP agent | controller
| :-) | True | neutron-dhcp-agent ||
f49a4b81-afd6-4b3d-b923-66c8f0517099 | Metadata agent | controller
| :-) | True | neutron-metadata-agent
|+--------------------------------------+--------------------+------------+-------+----------------+---------------------------+
HMM Or should I see only one if running all on the same box??
Thanks very much!!
-Chris
- Christopher T. Hull
333 Orchard Ave, Sunnyvale CA. 94085
(415) 385 4865
chrishull42 at gmail.com
http://chrishull.com
On Tue, Mar 8, 2016 at 6:47 PM, Kevin Benton <kevin at benton.pub> wrote:
> 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" <kevin at 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" <chrishull42 at 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 at lists.openstack.org
>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
>>>
>>>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-operators/attachments/20160308/2cda1a0d/attachment.html>
More information about the OpenStack-operators
mailing list