[tempest] No metadata route in test_dualnet* family
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
neutron |
Expired
|
Undecided
|
Unassigned |
Bug Description
We run tempest in such an environment that all ssh keys, personality files, etc. go through metadata service.
Which requires metadata route to 169.254.169.254 being provided by DHCP.
We faced rather complicated problem in scenario/
Networking configuration comprises of 4 steps:
1) Private network creation
2) Router creation and plugging it as a gateway in external network
3) Subnet creation
4) Adding router interface to the subnet
This sequence leads to that DHCP service provides static metadata route, and our scenario works.
That's how it is done in create_networks() from tempest/
But, prepare_network() of scenario/
DHCP service configuration in neutron regards this subnet isolated then (which is what I don't understand), therefore,
doesn't provide it with metadata route by default (force_
It really seems like Neutron has a bug handling such scenario: it doesn't update DHCP service configuration when router is created for subnet.
Also, AFAIU, all the upstream Jenkins dsvm tempest jobs running test_dualnet* get metadata from config drive,
that's possibly why they aren't affected.
tags: | added: l3-ipam-dhcp |
Changed in neutron: | |
importance: | Undecided → High |
Changed in neutron: | |
assignee: | nobody → Mohammed Ashraf (mohammed-asharaf) |
Changed in neutron: | |
status: | Confirmed → In Progress |
Changed in neutron: | |
assignee: | Mohammed Ashraf (mohammed-asharaf) → nobody |
Changed in neutron: | |
status: | In Progress → Incomplete |
importance: | High → Undecided |
Confirming. Once you kill dnsmasq and DHCP agent, and restart the agent, new configuration files are generated for the network that serve proper static routes pointing to router IP.