Sorry, maybe it's a stupid question, but is the l3-agent daemon
actually running?
root@cloud3:~# service neutron-l3-agent status
neutron-l3-agent start/running, process 17696
root@cloud3:~# neutron agent-list
Kevin/Antonio
Yeah router is still missing. The l3 agent is nto starting and I dont know
why. Im confident that I followed the guide exactly but when i start the
neutron server (systemctl start neutron-server.service) on the controller
node it wont start the l3 service...
[root@controller
Ok so I went ahead and rebooted everything just to clear everything out and
start up all the services - now it looks like everything is working. Go
figure. I still have no idea why wasnt starting but working now. I will try
and figure out why i couldnt start it manually and then when i rebooted
I think you do not have a l3 plugin configured in your neutron.conf -
therefore the l3 extension is not being loaded and the router resource does
not exist.
If the l3 plugin is not there just add it to service_plugins.
If the diagnosis is correct, can you post this question to ask.openstack.org
All,
So been following the Juno guide and now have arrived to the point where I
need to create the demo-router - but when I run the command this is what I
get:
[root@controller ~]# source demo-openrc.sh
[root@controller ~]# neutron router-create demo-router
Not Found (HTTP 404) (Request-ID:
Hi Salvatore,
Thanks for emailing! So from what I can see from the guide, Im only
supposed to edit the l3_agent.ini file on the network node. There is
nothing for l3_agent.ini on controller to edit from the guide. I did see
this as I continued to troubleshoot after my original email on the
The issue isn't with the configuration of the L3 agent. It's loading the l3
plugin on the Neutron server.
In /etc/neutron/neutron.conf you need to enable the router service
plugin.[1]
service_plugins = router
Hi Kevin,
Thanks but I have service_plugins = router on /etc/neutron.conf already on
all three nodes
On Tue, Nov 18, 2014 at 5:52 PM, Kevin Benton blak...@gmail.com wrote:
The issue isn't with the configuration of the L3 agent. It's loading the
l3 plugin on the Neutron server.
In
This config goes on whichever ones are running the neutron server process.
Can you include a neutron server.log file that begins from a server process
restart (service neutron-server restart)?
On Tue, Nov 18, 2014 at 3:33 PM, Amit Anand aan...@viimed.com wrote:
Hi Kevin,
Thanks but I have
Ok well the neutron server is running on my controller node. Here is the
log from a restart I just did:
2014-11-18 19:32:23.139 10165 INFO neutron.common.config [-] Logging
enabled!
2014-11-18 19:32:23.143 10165 INFO neutron.common.config [-] Config paste
file: /usr/share/neutron/api-paste.ini
So now if you run the ext-list command, is 'router' still missing?
On Tue, Nov 18, 2014 at 4:35 PM, Amit Anand aan...@viimed.com wrote:
Ok well the neutron server is running on my controller node. Here is the
log from a restart I just did:
2014-11-18 19:32:23.139 10165 INFO
11 matches
Mail list logo
