neutron-server waits unnecessarily for metadata service when DHCP is disabled
Bug #1828585 reported by
Daniel Alvarez
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) |
tags: | added: networking-ovn-proactive-backport-potential |
To post a comment you must log in.
Reviewed: https:/ /review. opendev. org/658383 /git.openstack. org/cgit/ openstack/ networking- ovn/commit/ ?id=1888f19d24b 17697d3a7cd5c5a 0ea550af3ddb66
Committed: https:/
Submitter: Zuul
Branch: master
commit 1888f19d24b1769 7d3a7cd5c5a0ea5 50af3ddb66
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: Iba3969e43c76ca 07fe840b84d8f81 f34bc7e5cd6
Closes-Bug: #1828585
Signed-off-by: Daniel Alvarez <email address hidden>