[OVN] Mech driver fails to delete DHCP options during subnet deletion
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Ubuntu Cloud Archive |
Fix Released
|
Undecided
|
Unassigned | ||
Ussuri |
Fix Released
|
High
|
Unassigned | ||
neutron |
Fix Released
|
Low
|
Rodolfo Alonso | ||
neutron (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Focal |
Fix Released
|
High
|
Unassigned |
Bug Description
== Original Bug Description ==
Snippet: https:/
I can't provide a link to a CI execution, I saw this error in an internal CI. I'm still investigating when this could happen.
== Ubuntu SRU Details ==
[Impact]
During subnet deletion the check in _remove_
ExternalNetwork
Traceback (most recent call last):
File "/opt/stack/
getattr(
File "/opt/stack/
self.
File "/opt/stack/
self.
File "/opt/stack/
dhcp_
KeyError: 'uuid'
The fix ensures this check handles a dictionary correctly.
[Test Case]
In case we don't have a recreate for this:
1) lxc launch ubuntu-daily:focal f1 && lxc exec f1 /bin/bash
2) sudo add-apt-repository -p proposed
3) sudo apt install python3-neutron
4) cd /usr/lib/
5) python3 -m unittest neutron.
6) re-run the test in step #5 after adding 'pdb.set_trace()' to the line before the check in neutron/
this way we can see what dhcp_options[
7) sudo add-apt-repository -r -p proposed
[Regression Potential]
This is a minimal change that is backward compatible with the previous check. The new check can still handle 'not None' in addition to handling an empty dictionary correctly. This has been fixed in Ubuntu Victoria packages (and above) since 2022-01-12, and has been fixed in the upstream stable/ussuri branch since 2021-10-25.
Changed in neutron: | |
status: | New → Incomplete |
Changed in neutron: | |
assignee: | nobody → Rodolfo Alonso (rodolfo-alonso-hernandez) |
Changed in neutron (Ubuntu): | |
status: | New → Fix Released |
Changed in neutron (Ubuntu Focal): | |
status: | New → Triaged |
importance: | Undecided → High |
Changed in cloud-archive: | |
status: | New → Fix Released |
description: | updated |
description: | updated |
description: | updated |
description: | updated |
description: | updated |
Is there any impact other than stale data in the DB? I would assume if subnet is deleted and new created, it's gonna have a different ID and will not cause any issues.