Some dhcp tap devices remain after tempest run
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
neutron |
Fix Released
|
Medium
|
Darragh O'Reilly | ||
Icehouse |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
After running tempest.
The sequence why these taps remain is:
- in dhcp_agent.py call_driver() is called with 'enable' for the network.
- in dhcp.py DeviceManager, setup() RPCs to creates the logical dhcp port and the tap device successfully. Setup() finally calls _set_default_
- the NetworkNotFound is caught by call_driver() and the network is not put into the cache. https:/
- then network_delete_end is processed, but this does nothing as there is no network in the cache.
https:/
It's not clear to me why _set_default_
And when the dhcp agent calls the 'restart' method, that calls enable(), but it then also calls DeviceManager.
Changed in neutron: | |
assignee: | nobody → Darragh O'Reilly (darragh-oreilly) |
status: | New → In Progress |
tags: | added: l3-ipam-dhcp |
Changed in neutron: | |
importance: | Undecided → Medium |
Changed in neutron: | |
milestone: | none → juno-1 |
status: | Fix Committed → Fix Released |
Changed in neutron: | |
milestone: | juno-1 → 2014.2 |
Fix proposed to branch: master /review. openstack. org/79282
Review: https:/