[Openstack] (Juno) Neutron router-create 404 error
Kevin Benton
blak111 at gmail.com
Wed Nov 19 01:02:27 UTC 2014
So now if you run the ext-list command, is 'router' still missing?
On Tue, Nov 18, 2014 at 4:35 PM, Amit Anand <aanand at 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 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
> 2014-11-18 19:32:23.325 10165 INFO neutron.manager [-] Loading core
> plugin: ml2
> 2014-11-18 19:32:23.399 10165 INFO neutron.plugins.ml2.managers [-]
> Configured type driver names: ['flat', 'gre']
> 2014-11-18 19:32:23.401 10165 INFO neutron.plugins.ml2.drivers.type_flat
> [-] Allowable flat physical_network names: []
> 2014-11-18 19:32:23.405 10165 INFO neutron.plugins.ml2.managers [-] Loaded
> type driver names: ['flat', 'gre']
> 2014-11-18 19:32:23.405 10165 INFO neutron.plugins.ml2.managers [-]
> Registered types: ['flat', 'gre']
> 2014-11-18 19:32:23.406 10165 INFO neutron.plugins.ml2.managers [-] Tenant
> network_types: ['gre']
> 2014-11-18 19:32:23.406 10165 INFO neutron.plugins.ml2.managers [-]
> Configured extension driver names: []
> 2014-11-18 19:32:23.406 10165 INFO neutron.plugins.ml2.managers [-] Loaded
> extension driver names: []
> 2014-11-18 19:32:23.407 10165 INFO neutron.plugins.ml2.managers [-]
> Registered extension drivers: []
> 2014-11-18 19:32:23.407 10165 INFO neutron.plugins.ml2.managers [-]
> Configured mechanism driver names: ['openvswitch']
> 2014-11-18 19:32:23.408 10165 INFO neutron.plugins.ml2.managers [-] Loaded
> mechanism driver names: ['openvswitch']
> 2014-11-18 19:32:23.408 10165 INFO neutron.plugins.ml2.managers [-]
> Registered mechanism drivers: ['openvswitch']
> 2014-11-18 19:32:23.419 10165 INFO neutron.plugins.ml2.managers [-]
> Initializing driver for type 'flat'
> 2014-11-18 19:32:23.420 10165 INFO neutron.plugins.ml2.drivers.type_flat
> [-] ML2 FlatTypeDriver initialization complete
> 2014-11-18 19:32:23.420 10165 INFO neutron.plugins.ml2.managers [-]
> Initializing driver for type 'gre'
> 2014-11-18 19:32:23.420 10165 INFO neutron.plugins.ml2.drivers.type_tunnel
> [-] gre ID ranges: [(1, 1000)]
> 2014-11-18 19:32:23.503 10165 INFO neutron.plugins.ml2.managers [-]
> Initializing mechanism driver 'openvswitch'
> 2014-11-18 19:32:23.504 10165 INFO neutron.plugins.ml2.plugin [-] Modular
> L2 Plugin initialization complete
> 2014-11-18 19:32:23.505 10165 INFO neutron.manager [-] Loading Plugin:
> router
> 2014-11-18 19:32:23.533 10165 INFO oslo.messaging._drivers.impl_rabbit [-]
> Connecting to AMQP server on controller:5672
> 2014-11-18 19:32:23.546 10165 INFO oslo.messaging._drivers.impl_rabbit [-]
> Connected to AMQP server on controller:5672
> 2014-11-18 19:32:23.551 10165 INFO neutron.db.l3_agentschedulers_db [-]
> Skipping period L3 agent status check because automatic router re
> scheduling is disabled.
> 2014-11-18 19:32:23.552 10165 INFO neutron.api.extensions [-] Initializing
> extension manager.
> 2014-11-18 19:32:23.553 10165 INFO neutron.api.extensions [-] Loaded
> extension: agent
> 2014-11-18 19:32:23.555 10165 INFO neutron.api.extensions [-] Loaded
> extension: allowed-address-pairs
> 2014-11-18 19:32:23.557 10165 INFO neutron.api.extensions [-] Loaded
> extension: dhcp_agent_scheduler
> 2014-11-18 19:32:23.558 10165 INFO neutron.api.extensions [-] Loaded
> extension: dvr
> 2014-11-18 19:32:23.559 10165 INFO neutron.api.extensions [-] Loaded
> extension: external-net
> 2014-11-18 19:32:23.560 10165 INFO neutron.api.extensions [-] Loaded
> extension: extra_dhcp_opt
> 2014-11-18 19:32:23.561 10165 INFO neutron.api.extensions [-] Loaded
> extension: extraroute
> 2014-11-18 19:32:23.567 10165 WARNING neutron.api.extensions [-] Extension
> fwaas not supported by any of loaded plugins
> 2014-11-18 19:32:23.568 10165 WARNING neutron.api.extensions [-] Extension
> flavor not supported by any of loaded plugins
> 2014-11-18 19:32:23.570 10165 INFO neutron.api.extensions [-] Loaded
> extension: router
> 2014-11-18 19:32:23.571 10165 INFO neutron.api.extensions [-] Loaded
> extension: ext-gw-mode
> 2014-11-18 19:32:23.573 10165 INFO neutron.api.extensions [-] Loaded
> extension: l3-ha
> 2014-11-18 19:32:23.575 10165 INFO neutron.api.extensions [-] Loaded
> extension: l3_agent_scheduler
> 2014-11-18 19:32:23.578 10165 WARNING neutron.api.extensions [-] Extension
> lbaas_agent_scheduler not supported by any of loaded plugins
> 2014-11-18 19:32:23.581 10165 WARNING neutron.api.extensions [-] Extension
> lbaas not supported by any of loaded plugins
> 2014-11-18 19:32:23.583 10165 WARNING neutron.api.extensions [-] Extension
> metering not supported by any of loaded plugins
> 2014-11-18 19:32:23.584 10165 INFO neutron.api.extensions [-] Loaded
> extension: multi-provider
> 2014-11-18 19:32:23.585 10165 INFO neutron.api.extensions [-] Loaded
> extension: binding
> 2014-11-18 19:32:23.586 10165 WARNING neutron.api.extensions [-] Extension
> port-security not supported by any of loaded plugins
> 2014-11-18 19:32:23.587 10165 INFO neutron.api.extensions [-] Loaded
> extension: provider
> 2014-11-18 19:32:23.588 10165 INFO neutron.api.extensions [-] Loaded
> extension: quotas
> 2014-11-18 19:32:23.589 10165 WARNING neutron.api.extensions [-] Extension
> routed-service-insertion not supported by any of loaded plugin
> s
> 2014-11-18 19:32:23.590 10165 WARNING neutron.api.extensions [-] Extension
> router-service-type not supported by any of loaded plugins
> 2014-11-18 19:32:23.593 10165 INFO neutron.api.extensions [-] Loaded
> extension: security-group
> 2014-11-18 19:32:23.594 10165 WARNING neutron.api.extensions [-] Extension
> service-type not supported by any of loaded plugins
> 2014-11-18 19:32:23.597 10165 WARNING neutron.api.extensions [-] Extension
> vpnaas not supported by any of loaded plugins
> 2014-11-18 19:32:23.597 10165 INFO neutron.api.extensions [-] Extension
> 'agent' provides no backward compatibility map for extended attri
> butes
> 2014-11-18 19:32:23.598 10165 INFO neutron.api.extensions [-] Extension
> 'Allowed Address Pairs' provides no backward compatibility map fo
> r extended attributes
> 2014-11-18 19:32:23.598 10165 INFO neutron.api.extensions [-] Extension
> 'Distributed Virtual Router' provides no backward compatibility m
> ap for extended attributes
> 2014-11-18 19:32:23.598 10165 INFO neutron.api.extensions [-] Extension
> 'Neutron Extra Route' provides no backward compatibility map for
> extended attributes
> 2014-11-18 19:32:23.613 10165 INFO keystonemiddleware.auth_token [-]
> Starting keystone auth_token middleware
> 2014-11-18 19:32:23.615 10165 INFO keystonemiddleware.auth_token [-] Using
> /tmp/keystone-signing-Igp6Tk as cache directory for signing ce
> rtificate
> 2014-11-18 19:32:23.623 10165 INFO neutron.service [-] Neutron service
> started, listening on 0.0.0.0:9696
> 2014-11-18 19:32:23.623 10165 INFO oslo.messaging._drivers.impl_rabbit [-]
> Connecting to AMQP server on controller:5672
> 2014-11-18 19:32:23.631 10165 INFO neutron.wsgi [-] (10165) wsgi starting
> up on http://0.0.0.0:9696/
> 2014-11-18 19:32:23.634 10165 INFO oslo.messaging._drivers.impl_rabbit [-]
> Connected to AMQP server on controller:5672
>
> On Tue, Nov 18, 2014 at 7:17 PM, Kevin Benton <blak111 at gmail.com> wrote:
>
>> 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 <aanand at viimed.com> wrote:
>>
>>> 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 <blak111 at 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 /etc/neutron/neutron.conf you need to enable the router service
>>>> plugin.[1]
>>>> service_plugins = router
>>>>
>>>>
>>>> https://github.com/openstack/neutron/blob/c2b1594ad878b1897468210ccb89fc0d0c4146c4/etc/neutron.conf#L72
>>>>
>>>> On Tue, Nov 18, 2014 at 2:10 PM, Amit Anand <aanand at viimed.com> wrote:
>>>>
>>>>> 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
>>>>> controller node:
>>>>>
>>>>> systemctl status neutron-l3-agent.service
>>>>> neutron-l3-agent.service - OpenStack Neutron Layer 3 Agent
>>>>> Loaded: loaded (/usr/lib/systemd/system/neutron-l3-agent.service;
>>>>> disabled)
>>>>> Active: failed (Result: exit-code) since Tue 2014-11-18 16:29:19
>>>>> EST; 22min ago
>>>>> Process: 6063 ExecStart=/usr/bin/neutron-l3-agent --config-file
>>>>> /usr/share/neutron/neutron-dist.conf --config-file
>>>>> /etc/neutron/neutron.conf --config-file /etc/neutron/l3_agent.ini
>>>>> --config-file /etc/neutron/fwaas_driver.ini --log-file
>>>>> /var/log/neutron/l3-agent.log (code=exited, status=1/FAILURE)
>>>>> Main PID: 6063 (code=exited, status=1/FAILURE)
>>>>>
>>>>> Nov 18 16:29:19 controller systemd[1]: Started OpenStack Neutron Layer
>>>>> 3 Agent.
>>>>> Nov 18 16:29:19 controller systemd[1]: neutron-l3-agent.service: main
>>>>> process exited, code=exited, status=1/FAILURE
>>>>> Nov 18 16:29:19 controller systemd[1]: Unit neutron-l3-agent.service
>>>>> entered failed state.
>>>>> Nov 18 16:31:18 controller systemd[1]: Stopped OpenStack Neutron Layer
>>>>> 3 Agent.
>>>>>
>>>>>
>>>>> And when I went and looked at these logs I see:
>>>>>
>>>>> [root at controller neutron]# more l3-agent.log
>>>>> 2014-11-18 16:29:19.519 6063 INFO neutron.common.config [-] Logging
>>>>> enabled!
>>>>> 2014-11-18 16:29:19.520 6063 ERROR neutron.agent.l3_agent [-] An
>>>>> interface driver must be specified
>>>>>
>>>>> So Im not sure if thats what you are talking about - Am I supposed to
>>>>> do what I did for the controller node l3_agent.ini I did for the network
>>>>> node (below)? What about the compute node? Am I not sure what you mean by
>>>>> having l3 plugin not configured in my neutron.conf. How do I do that? I
>>>>> have service_plugins = router currently. And which neutron.conf do I need
>>>>> to edit as I have 3, one for each node. I will def post this answer up and
>>>>> answered when finished on openstack as I cant find any relevant question
>>>>> asked about this. Thank you very much!!
>>>>>
>>>>> *To configure the Layer-3 (L3) agent*
>>>>>
>>>>> The Layer-3 (L3) agent
>>>>> <http://docs.openstack.org/juno/install-guide/install/yum/content/neutron-network-node.html#> provides
>>>>> routing services for virtual networks.
>>>>>
>>>>> -
>>>>>
>>>>> Edit the /etc/neutron/l3_agent.ini file and complete the following
>>>>> actions:
>>>>> 1.
>>>>>
>>>>> In the [DEFAULT] section, configure the driver, enable network
>>>>> namespaces
>>>>> <http://docs.openstack.org/juno/install-guide/install/yum/content/neutron-network-node.html#>,
>>>>> and configure the external network bridge:
>>>>> [image: Select Text]
>>>>> 1
>>>>> 2
>>>>> 3
>>>>> 4
>>>>> 5
>>>>> [DEFAULT]
>>>>> ...
>>>>> interface_driver =
>>>>> neutron.agent.linux.interface.OVSInterfaceDriver
>>>>> use_namespaces = True
>>>>> external_network_bridge = br-ex
>>>>> 2.
>>>>>
>>>>> (Optional) To assist with troubleshooting, enable verbose
>>>>> logging in the [DEFAULT] section:
>>>>> [image: Select Text]
>>>>> 1
>>>>> 2
>>>>> 3
>>>>> [DEFAULT]
>>>>> ...
>>>>> verbose = True
>>>>>
>>>>>
>>>>>
>>>>> On Tue, Nov 18, 2014 at 4:18 PM, Salvatore Orlando <
>>>>> sorlando at nicira.com> wrote:
>>>>>
>>>>>> 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 (if it's not already there).
>>>>>> This is probably a typical problem that many users face when they
>>>>>> start deploying neutron.
>>>>>>
>>>>>> Salvatore
>>>>>>
>>>>>> On 18 November 2014 22:08, Amit Anand <aanand at viimed.com> wrote:
>>>>>>
>>>>>>> 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 at controller ~]# source demo-openrc.sh
>>>>>>> [root at controller ~]# neutron router-create demo-router
>>>>>>> Not Found (HTTP 404) (Request-ID:
>>>>>>> req-00fa2ff1-dfb6-4d28-976c-be0f3d500e64
>>>>>>>
>>>>>>> There is not much more in --debug or logs than that error above. I
>>>>>>> have no idea why this is happening. I DID notice one strange thing and
>>>>>>> maybe somebody will be able to tell me whats wrong. I configured the
>>>>>>> controller and network nodes per guide and to test, run neutron ext-list
>>>>>>> for controller node when finished and neutron agent-list for both compute
>>>>>>> and network nodes when they are finished. So the weird thing is, for the
>>>>>>> network and compute node this is the output:
>>>>>>>
>>>>>>> neutron agent-list
>>>>>>>
>>>>>>> +--------------------------------------+--------------------+----------+-------+----------------+---------------------------+
>>>>>>> | id | agent_type | host
>>>>>>> | alive | admin_state_up | binary |
>>>>>>>
>>>>>>> +--------------------------------------+--------------------+----------+-------+----------------+---------------------------+
>>>>>>> | 037f3155-4518-4e67-994f-6703bb860a78 | Metadata agent |
>>>>>>> network | :-) | True | neutron-metadata-agent |
>>>>>>> | 3463361e-bf7a-4b01-afa8-9a4752992a17 | Open vSwitch agent |
>>>>>>> network | :-) | True | neutron-openvswitch-agent |
>>>>>>> | 561e337e-cb7e-4c98-991a-3a08873464ad | Open vSwitch agent |
>>>>>>> compute1 | :-) | True | neutron-openvswitch-agent |
>>>>>>> | fd1100dd-470c-44ba-b017-3ccd08c3f8fe | DHCP agent |
>>>>>>> network | :-) | True | neutron-dhcp-agent |
>>>>>>>
>>>>>>> +--------------------------------------+--------------------+----------+-------+----------------+---------------------------+
>>>>>>>
>>>>>>> But in the guide it shows neutron-l3-agent running as well! And for
>>>>>>> the controller the output is:
>>>>>>>
>>>>>>>
>>>>>>> [root at controller ~]# neutron ext-list
>>>>>>> +-----------------------+--------------------------+
>>>>>>> | alias | name |
>>>>>>> +-----------------------+--------------------------+
>>>>>>> | security-group | security-group |
>>>>>>> | provider | Provider Network |
>>>>>>> | binding | Port Binding |
>>>>>>> | quotas | Quota management support |
>>>>>>> | agent | agent |
>>>>>>> | dhcp_agent_scheduler | DHCP Agent Scheduler |
>>>>>>> | external-net | Neutron external network |
>>>>>>> | multi-provider | Multi Provider Network |
>>>>>>> | allowed-address-pairs | Allowed Address Pairs |
>>>>>>> | extra_dhcp_opt | Neutron Extra DHCP opts |
>>>>>>> +-----------------------+--------------------------+
>>>>>>>
>>>>>>> As you can see, there a few things missing that are in the Juno
>>>>>>> guide example such as l3_agent_scheduler and ext-gw-mode and router among
>>>>>>> others...Am I not turning them on somehow? I dont think I missed anything
>>>>>>> as Ive done this twice already now and I dont think I can do all the
>>>>>>> configuring again without going crazy :-) Appreciate any help!
>>>>>>>
>>>>>>> neutron ext-list
>>>>>>> +-----------------------+-----------------------------------------------+
>>>>>>> | alias | name |
>>>>>>> +-----------------------+-----------------------------------------------+
>>>>>>> | security-group | security-group |
>>>>>>> | l3_agent_scheduler | L3 Agent Scheduler |
>>>>>>> | ext-gw-mode | Neutron L3 Configurable external gateway mode |
>>>>>>> | binding | Port Binding |
>>>>>>> | provider | Provider Network |
>>>>>>> | agent | agent |
>>>>>>> | quotas | Quota management support |
>>>>>>> | dhcp_agent_scheduler | DHCP Agent Scheduler |
>>>>>>> | l3-ha | HA Router extension |
>>>>>>> | multi-provider | Multi Provider Network |
>>>>>>> | external-net | Neutron external network |
>>>>>>> | router | Neutron L3 Router |
>>>>>>> | allowed-address-pairs | Allowed Address Pairs |
>>>>>>> | extraroute | Neutron Extra Route |
>>>>>>> | extra_dhcp_opt | Neutron Extra DHCP opts |
>>>>>>> | dvr | Distributed Virtual Router |
>>>>>>> +-----------------------+------------------------------------------------
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> _______________________________________________
>>>>>>> Mailing list:
>>>>>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
>>>>>>> Post to : openstack at lists.openstack.org
>>>>>>> Unsubscribe :
>>>>>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
>>>>>>>
>>>>>>>
>>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> Mailing list:
>>>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
>>>>> Post to : openstack at lists.openstack.org
>>>>> Unsubscribe :
>>>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
>>>>>
>>>>>
>>>>
>>>>
>>>> --
>>>> Kevin Benton
>>>>
>>>
>>>
>>
>>
>> --
>> Kevin Benton
>>
>
>
--
Kevin Benton
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack/attachments/20141118/dd1f6162/attachment.html>
More information about the Openstack
mailing list