neutron-server waits unnecessarily for metadata service when DHCP is disabled

Bug #1828585 reported by Daniel Alvarez
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
networking-ovn
Fix Released
Undecided
Daniel Alvarez

Bug Description

When a port gets bound to a hypervisor, neutron-server will wait up to 15 seconds until metadata is provisioned before transitioning the port to ACTIVE.

Currently for OVN metadata service, a static route is injected via DHCP to 169.254.169.254 via the metadata port so if DHCP is disabled, neutron-server will always wait until timeout since the metadata service cannot be provisioned.

Until we implement some other way for serving metadata, we're depending on DHCP. Anyways, neutron-server shouldn't wait if the port doesn't belong to any IPv4 subnet with DHCP enabled.

Changed in networking-ovn:
assignee: nobody → Daniel Alvarez (dalvarezs)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to networking-ovn (master)

Reviewed: https://review.opendev.org/658383
Committed: https://git.openstack.org/cgit/openstack/networking-ovn/commit/?id=1888f19d24b17697d3a7cd5c5a0ea550af3ddb66
Submitter: Zuul
Branch: master

commit 1888f19d24b17697d3a7cd5c5a0ea550af3ddb66
Author: Daniel Alvarez <email address hidden>
Date: Fri May 10 16:49:34 2019 +0200

    Don't wait for metadata service unnecessarily

    Before neutron-server transitions a port to ACTIVE, it'll wait
    until the metadata service has been provisioned on that hypervisor.
    If the port doesn't belong to any IPv4 subnet with DHCP enabled,
    there's no need to wait for it.

    Change-Id: Iba3969e43c76ca07fe840b84d8f81f34bc7e5cd6
    Closes-Bug: #1828585
    Signed-off-by: Daniel Alvarez <email address hidden>

Changed in networking-ovn:
status: New → Fix Released
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to networking-ovn (stable/queens)

Fix proposed to branch: stable/queens
Review: https://review.opendev.org/659760

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to networking-ovn (stable/rocky)

Fix proposed to branch: stable/rocky
Review: https://review.opendev.org/659761

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to networking-ovn (stable/stein)

Fix proposed to branch: stable/stein
Review: https://review.opendev.org/659763

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to networking-ovn (stable/stein)

Reviewed: https://review.opendev.org/659763
Committed: https://git.openstack.org/cgit/openstack/networking-ovn/commit/?id=71a29c8c3be8ea33c0cf20f1723665c61f99d5df
Submitter: Zuul
Branch: stable/stein

commit 71a29c8c3be8ea33c0cf20f1723665c61f99d5df
Author: Daniel Alvarez <email address hidden>
Date: Fri May 10 16:49:34 2019 +0200

    Don't wait for metadata service unnecessarily

    Before neutron-server transitions a port to ACTIVE, it'll wait
    until the metadata service has been provisioned on that hypervisor.
    If the port doesn't belong to any IPv4 subnet with DHCP enabled,
    there's no need to wait for it.

    Change-Id: Iba3969e43c76ca07fe840b84d8f81f34bc7e5cd6
    Closes-Bug: #1828585
    Signed-off-by: Daniel Alvarez <email address hidden>
    (cherry picked from commit 1888f19d24b17697d3a7cd5c5a0ea550af3ddb66)

tags: added: in-stable-stein
tags: added: networking-ovn-proactive-backport-potential
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to networking-ovn (stable/rocky)

Reviewed: https://review.opendev.org/659761
Committed: https://git.openstack.org/cgit/openstack/networking-ovn/commit/?id=7442d0c120b5723fd5f09fa7b1e0b201852ad3b5
Submitter: Zuul
Branch: stable/rocky

commit 7442d0c120b5723fd5f09fa7b1e0b201852ad3b5
Author: Daniel Alvarez <email address hidden>
Date: Fri May 10 16:49:34 2019 +0200

    Don't wait for metadata service unnecessarily

    Before neutron-server transitions a port to ACTIVE, it'll wait
    until the metadata service has been provisioned on that hypervisor.
    If the port doesn't belong to any IPv4 subnet with DHCP enabled,
    there's no need to wait for it.

    Change-Id: Iba3969e43c76ca07fe840b84d8f81f34bc7e5cd6
    Closes-Bug: #1828585
    Signed-off-by: Daniel Alvarez <email address hidden>
    (cherry picked from commit 1888f19d24b17697d3a7cd5c5a0ea550af3ddb66)

tags: added: in-stable-rocky
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to networking-ovn (stable/queens)

Reviewed: https://review.opendev.org/659760
Committed: https://git.openstack.org/cgit/openstack/networking-ovn/commit/?id=b80adc1b9fb80866b6e0e3a8ff60e3720bdaa9d0
Submitter: Zuul
Branch: stable/queens

commit b80adc1b9fb80866b6e0e3a8ff60e3720bdaa9d0
Author: Daniel Alvarez <email address hidden>
Date: Fri May 10 16:49:34 2019 +0200

    Don't wait for metadata service unnecessarily

    Before neutron-server transitions a port to ACTIVE, it'll wait
    until the metadata service has been provisioned on that hypervisor.
    If the port doesn't belong to any IPv4 subnet with DHCP enabled,
    there's no need to wait for it.

    Change-Id: Iba3969e43c76ca07fe840b84d8f81f34bc7e5cd6
    Closes-Bug: #1828585
    Signed-off-by: Daniel Alvarez <email address hidden>
    (cherry picked from commit 1888f19d24b17697d3a7cd5c5a0ea550af3ddb66)

tags: added: in-stable-queens
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/networking-ovn 7.0.0.0b1

This issue was fixed in the openstack/networking-ovn 7.0.0.0b1 development milestone.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/networking-ovn 4.0.4

This issue was fixed in the openstack/networking-ovn 4.0.4 release.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/networking-ovn 6.0.1

This issue was fixed in the openstack/networking-ovn 6.0.1 release.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/networking-ovn 5.1.0

This issue was fixed in the openstack/networking-ovn 5.1.0 release.

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.