Metadata IP is resolved locally by Windows by default, causing big delay in URL access
Bug #1460793 reported by
Eugene Nikanorov
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
neutron |
Fix Released
|
Medium
|
Eugene Nikanorov |
Bug Description
WIth private network plugged into a router and router serving metadata:
When windows accesses metadata url, it tries to resolve mac address of it despite of routing table that tells to go to default gateway. That is because of nature of 169.254 which is considered local by default.
Such behavior causes big delay before connection could be established.
This, in turn, causes lots of issues during cloud init phase: slowness, timeouts, etc.
The workaround could be to add explicit route to a subnet, e.g. 169.254.169.254/32 via subnet's default gateway.
It makes sense to let DHCP agent inject such route by default via dnsmasq config.
tags: | added: l3-ipam-dhcp |
Changed in neutron: | |
milestone: | none → liberty-1 |
status: | Fix Committed → Fix Released |
Changed in neutron: | |
milestone: | liberty-1 → 7.0.0 |
To post a comment you must log in.
Fix proposed to branch: master /review. openstack. org/187431
Review: https:/