DHCP entries for floating IP ports are not needed really

Bug #1913269 reported by Slawek Kaplonski
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
neutron
Fix Released
Medium
Slawek Kaplonski

Bug Description

When Floating IP is created, there is unbound port created for it too. And if subnet on which is this port has enabled DHCP, then this port has entry in the dnsmasq leases file as any other port. But this isn't really needed in such case.
Similary, there is no need to configure by DHCP agent ports which belongs to the routers. In some cases it may decrease load of the agents a bit.

Revision history for this message
Slawek Kaplonski (slaweq) wrote :
Changed in neutron:
status: New → In Progress
tags: added: l3-ipam-dhcp
Revision history for this message
LIU Yulong (dragon889) wrote :

Maybe we should disable the DHCP for the network (external network, HA network and so on) at the begining. Yes, it is the bug:
https://bugs.launchpad.net/neutron/+bug/1911864

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

I know cases when VMs are created on external network - disabling this ability will affect users.

Aren't HA network subnets created with dhcp disabled already?

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/neutron 17.1.1

This issue was fixed in the openstack/neutron 17.1.1 release.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/neutron 18.0.0.0rc1

This issue was fixed in the openstack/neutron 18.0.0.0rc1 release candidate.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/neutron 15.3.4

This issue was fixed in the openstack/neutron 15.3.4 release.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/neutron 16.3.2

This issue was fixed in the openstack/neutron 16.3.2 release.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to neutron (stable/rocky)

Reviewed: https://review.opendev.org/c/openstack/neutron/+/777123
Committed: https://opendev.org/openstack/neutron/commit/2f662482489b62667759d05164013e2ef6b7da6d
Submitter: "Zuul (22348)"
Branch: stable/rocky

commit 2f662482489b62667759d05164013e2ef6b7da6d
Author: Slawek Kaplonski <email address hidden>
Date: Tue Jan 26 11:22:39 2021 +0100

    Don't configure dnsmasq entries for "network" ports

    Ports with device_owner like:
    * floating_ip,
    * DHCP,
    * some types of router ports, like: HA interface interface,
    don't need to be configured in the dnsmasq file.
    So there is no need to reload dnsmasq every time when such port is
    added/updated to the network.

    This patch adds skip in such case which should improve load on the
    Neutron DHCP agent.

    Conflicts:
        neutron/agent/linux/dhcp.py
        neutron/agent/dhcp/agent.py

    # Fix for Rocky gate (backports to other branches didn't really
    # that depends-on:
    Depends-On: https://review.opendev.org/c/openstack/neutron-tempest-plugin/+/786657

    Closes-Bug: #1913269
    Change-Id: I63221507713b941c261cdf88781133149da8ab8d
    (cherry picked from commit e4bbeee2060058d079885339e99ef7e6e366de16)

tags: added: in-stable-rocky
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/neutron queens-eol

This issue was fixed in the openstack/neutron queens-eol release.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/neutron rocky-eol

This issue was fixed in the openstack/neutron rocky-eol release.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/neutron stein-eol

This issue was fixed in the openstack/neutron stein-eol release.

Changed in neutron:
status: In Progress → Fix Released
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.