warnings for the lack of dhcp agent

Bug #1519410 reported by Jaume Devesa
This bug affects 2 people
Affects Status Importance Assigned to Milestone

Bug Description

When creating a VM using MidoNet v5 + Kilo, we see this error:

2015-11-24 23:44:30.674 4719 DEBUG midonet.neutron.plugin_v2 [req-ead126bb-819a-49e4-9c0d-c359234c629e ] MidonetPluginV2.get_network called: id=u'22c5858d-5020-4458-9fd9-0b98d1dcd6f9' get_network /usr/lib/python2.7/site-packages/midonet/neutron/plugin_v2.py:101
2015-11-24 23:44:30.694 4719 WARNING neutron.scheduler.dhcp_agent_scheduler [req-ead126bb-819a-49e4-9c0d-c359234c629e ] No more DHCP agents
2015-11-24 23:44:30.694 4719 WARNING neutron.api.rpc.agentnotifiers.dhcp_rpc_agent_api [req-ead126bb-819a-49e4-9c0d-c359234c629e ] Unable to schedule network 22c5858d-5020-4458-9fd9-0b98d1dcd6f9: no agents available; will retry on subsequent port and subnet creation eve
2015-11-24 23:44:30.698 4719 ERROR neutron.api.rpc.agentnotifiers.dhcp_rpc_agent_api [req-ead126bb-819a-49e4-9c0d-c359234c629e ] Will not send event port_create_end for network 22c5858d-5020-4458-9fd9-0b98d1dcd6f9: no agent available. Payload: {'port': {'status': 'ACTIV
E', 'binding:host_id': u'sa-lab-03', 'allowed_address_pairs': [], 'device_owner': u'compute:None', 'binding:profile': None, 'fixed_ips': [{'subnet_id': u'ffe7bcbe-7ea1-4543-adc3-b9058cb7ee85', 'ip_address': u''}], 'id': '9bb7a5da-5b94-41a9-a579-81486b539fe3',
'security_groups': [u'9e57dc9f-aa60-4893-bd76-06c7b41f479a'], 'device_id': u'98b00adc-1fd7-4053-b4d4-88a8c4d41e9a', 'name': '', 'admin_state_up': True, 'network_id': u'22c5858d-5020-4458-9fd9-0b98d1dcd6f9', 'tenant_id': u'9df82354086c4d138acd052eaf09e7c4', 'binding:vif_
details': {'port_filter': True}, 'binding:vnic_type': 'normal', 'binding:vif_type': 'midonet', 'mac_address': 'fa:16:3e:c7:99:31'}}
2015-11-24 23:44:30.699 4719 INFO neutron.wsgi [req-ead126bb-819a-49e4-9c0d-c359234c629e ] - - [24/Nov/2015 23:44:30] "POST /v2.0/ports.json HTTP/1.1" 201 908 0.177428
2015-11-24 23:44:30.720 4719 INFO neutron.wsgi [req-77cfa245-5089-4fb3-8b05-7d0d8745bd46 ] - - [24/Nov/2015 23:44:30] "GET

This error is not shown using MidoNet 2015.06 + Kilo. My guess is that, since Kilo plugin defines the dhcp agent scheduler extension:


and MidoNet v5 does not need any dhcp agent, this error is thrown.

Revision history for this message
YAMAMOTO Takashi (yamamoto) wrote :

your guess is right.
the warning itself is expected.
do you have any functional probrems?

Revision history for this message
Jaume Devesa (devvesa) wrote :

I think there are not related functional problems... but it is ugly to see these traces. I propose to keep this bug in a low critical mode.

Changed in networking-midonet:
importance: Undecided → Medium
Revision history for this message
YAMAMOTO Takashi (yamamoto) wrote :

i agree the current situation isn't ideal.

Changed in networking-midonet:
status: New → Confirmed
Revision history for this message
Hiroyuki Ito (ito-hiroyuki-01) wrote :

With commit: 7d42ee769cdd4f4dc7b2ca1d85557bc471ce4b7e for neutron (target is Mitaka), it looks the error message isn't be outputted. (but the warning message is still outputted.)
For kilo version, how about setting "dhcp_agent_notification=false" in neutron.conf? I suppose MidoNet doesn't need notifications for dhcp agent and this setting makes no functional impacts.

Revision history for this message
Antonio Ojea (aojea) wrote :

We should close as Won't fix, kilo is EOL

Changed in networking-midonet:
status: Confirmed → Fix Committed
status: Fix Committed → Confirmed
summary: - Error traced notifying dhcp agent in Kilo
+ warnings for the lack of dhcp agent
Changed in networking-midonet:
milestone: 2015.1.2 → none
importance: Medium → Wishlist
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.