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 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 /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 <aan...@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@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 <sorla...@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 <aan...@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@controller ~]# source demo-openrc.sh >>>>> [root@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@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@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@lists.openstack.org >>> Unsubscribe : >>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack >>> >>> >> >> >> -- >> Kevin Benton >> > > -- Kevin Benton
_______________________________________________ Mailing list: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack Post to : openstack@lists.openstack.org Unsubscribe : http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack
