neutron not schedule the network to DHCP agent

Bug #1289082 reported by li,chen
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
neutron
New
Undecided
Unassigned

Bug Description

Hi list,

I’m working on CentOS 6.4 + Havana.

When I create a new network, I get error message in /var/log/neutron/server.log:

Run command:

neutron net-create test-network03

Output in /var/log/neutron/server.log:

2014-03-06 13:28:37.078 21277 ERROR neutron.api.rpc.agentnotifiers.dhcp_rpc_agent_api [-] No DHCP agents are associated with network 'b02112bf-9fe5-4053-8ced-e08bd2547b49'. Unable to send notification for 'network_create_end' with payload: {'network': {'status': 'ACTIVE', 'subnets': [], 'name': u'test-network03', 'provider:physical_network': None, 'admin_state_up': True, 'tenant_id': u'1e57be810f854bcdb73901567140ac48', 'provider:network_type': u'gre', 'shared': False, 'id': 'b02112bf-9fe5-4053-8ced-e08bd2547b49', 'provider:segmentation_id': 3L}}

Run command:

neutron subnet-create test-network03 90.1.130.0/24

Output in /var/log/neutron/server.log:

2014-03-06 13:30:43.414 21277 INFO urllib3.connectionpool [-] Starting new HTTP connection (1): host-keystone
2014-03-06 13:30:43.516 21277 ERROR neutron.api.rpc.agentnotifiers.dhcp_rpc_agent_api [-] No DHCP agents are associated with network 'b02112bf-9fe5-4053-8ced-e08bd2547b49'. Unable to send notification for 'subnet_create_end' with payload: {'subnet': {'name': '', 'enable_dhcp': True, 'network_id': u'b02112bf-9fe5-4053-8ced-e08bd2547b49', 'tenant_id': u'1e57be810f854bcdb73901567140ac48', 'dns_nameservers': [], 'allocation_pools': [{'start': '90.1.130.2', 'end': '90.1.130.254'}], 'host_routes': [], 'ip_version': 4, 'gateway_ip': '90.1.130.1', 'cidr': u'90.1.130.0/24', 'id': '25d1653f-d043-41e6-9206-d020cab041b1'}}

I do have an active DHCP agent:

neutron agent-list

+--------------------------------------+--------------------+-------------+-------+----------------+
| id | agent_type | host | alive | admin_state_up |
+--------------------------------------+--------------------+-------------+-------+----------------+
| 246dd973-ebfd-4948-b655-6171f5866b19 | DHCP agent | b-compute05 | :-) | True |
| 5c6260cf-15c2-4757-9170-68be2d5e5d8b | Open vSwitch agent | b-compute05 | :-) | True |
+--------------------------------------+--------------------+-------------+-------+----------------+

Anyone know why this happen ?????

Thanks.
-chen

li,chen (chen-li)
description: updated
Revision history for this message
Lingfeng Xiong (xionglingfeng) wrote :

I'm experiencing the same situation. My setup is a XenServer based multi-node installation. Every time when I trying to create a network in controller node, the log shows that warning. Also, all VM belonging to that network will get the first available IP address(usually x.x.x.2), not the start IP address I specified.

Revision history for this message
Oleg Bondarev (obondarev) wrote :

This is a dupication of bug 1289130 Please see bug description and corresponding fix on gerrit for more details.

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.