This bug was initially created as a copy of Bug #2259968

• I am copying this bug because:

Customer found a workaround for this problem and closed the case linked to the original BZ.

This bug is being copied to address the issue of the reserved_dhcp_port feature not working on the Neutron/DHCP agent side.

There's very little/no documentation on this feature upstream. I am also not sure if this is something supported by ML2/OVN (I don't think it is).

• Original BZ description:

Customer is putting together a new OSP 17.1 baremetal setup in lab, and encounters issues at node cleaning step (step 8 of procedure in ref.[1]).

The baremetal node makes several attempts to PXE boot but does not receive a response from the director server.

(overcloud) [stack@edtnabtf-pd03ye06-02 ~]$ openstack baremetal node list
------------------------------------------------------------------------------------------------------------------------------+

------------------------------------------------------------------------------------------------------------------------------+

------------------------------------------------------------------------------------------------------------------------------+

Packet capture from the OSP Controller shows that the DHCP request was received by director
and that a response is received.

Looking into /var/log/containers/ironic-inspector/dnsmasq.log, we can see that the DHCPDISCOVER from the baremetal server is being ignored by the OSP Controller.

We need to know why the ironic-inspector is ignoring DHCP requests from the baremetal server.

[1] https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/17.1/html-single/configuring_the_bare_metal_provisioning_service/index#proc_enrolling-a-bare-metal-node-with-an-inventory-file_bare-metal-post-deployment

Version-Release number of selected component (if applicable):
RHOSP 17.1

How reproducible:
Always

Steps to Reproduce:
1. Follow procedure in ref.[1] above
2.
3.

Actual results:
At procedure step 8, node cleaning fails

Expected results:
Node cleaning succeeds.

Additional info: