Service Subnets - DHCP port creation fails
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
neutron |
Fix Released
|
High
|
John Davidge |
Bug Description
Service Subnets[1] were added in Newton.
The TL;DR is that a subnet can be created/updated with one or more service_types corresponding to a port device owner. If a subnet has one or more service_types, then only ports with a matching device owner can be created on the subnet.
If a service subnet is created with dhcp enabled, automatic dhcp port creation fails, because the port device owner does not match the subnet's service_types.
The port creation is re-attempted over and over, and the subnet remains without dhcp.
Steps to recreate:
NOTE: THIS REQUIRES INSTALLING OPENSTACKCLIENT FROM MASTER
$ openstack network create test-net
$ openstack subnet create test-subnet --subnet-range 10.1.0.0/24 \
--service-type compute:nova --network test-net
Then take a look in the q-svc logs.
[1] http://
description: | updated |
Changed in neutron: | |
milestone: | ocata-1 → ocata-2 |
tags: | added: neutron-proactive-backport-potential |
Actually, I had this in the back of my mind at one point. I didn't prioritize the issue because the use cases that I had in mind don't require DHCP enabled on the subnet. Then, I forgot to follow up on it. That was my fault.
That's not a good excuse. This should work. The DHCP server needs a port on such a subnet and we need to allow it. It should be a pretty easy fix. Thanks for filing this bug report.