dhcp._release_lease shouldn't stacktrace when a device isn't found since it could be legitimately gone
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
neutron |
Expired
|
Medium
|
Unassigned | ||
tempest |
Invalid
|
Undecided
|
Unassigned |
Bug Description
This kind of stuff is really annoying in debugging failures in the gate since I think it's a known failure during cleanup of ports when deleting an instance, so we shouldn't stacktrace this and log as an error, just handle it in the code and move on.
2015-07-22 09:30:43.303 ERROR neutron.
2015-07-22 09:30:43.303 8230 ERROR neutron.
2015-07-22 09:30:43.303 8230 ERROR neutron.
2015-07-22 09:30:43.303 8230 ERROR neutron.
2015-07-22 09:30:43.303 8230 ERROR neutron.
2015-07-22 09:30:43.303 8230 ERROR neutron.
2015-07-22 09:30:43.303 8230 ERROR neutron.
2015-07-22 09:30:43.303 8230 ERROR neutron.
2015-07-22 09:30:43.303 8230 ERROR neutron.
2015-07-22 09:30:43.303 8230 ERROR neutron.
2015-07-22 09:30:43.303 8230 ERROR neutron.
2015-07-22 09:30:43.303 8230 ERROR neutron.
2015-07-22 09:30:43.303 8230 ERROR neutron.
2015-07-22 09:30:43.303 8230 ERROR neutron.
2015-07-22 09:30:43.303 8230 ERROR neutron.
2015-07-22 09:30:43.303 8230 ERROR neutron.
2015-07-22 09:30:43.303 8230 ERROR neutron.
2015-07-22 09:30:43.303 8230 ERROR neutron.
2015-07-22 09:30:43.303 8230 ERROR neutron.
2015-07-22 09:30:43.303 8230 ERROR neutron.
2015-07-22 09:30:43.303 8230 ERROR neutron.
2015-07-22 09:30:43.303 8230 ERROR neutron.
Changed in neutron: | |
assignee: | nobody → Sridhar Gaddam (sridhargaddam) |
Changed in neutron: | |
status: | New → Confirmed |
importance: | Undecided → Medium |
Changed in neutron: | |
status: | Confirmed → In Progress |
Changed in tempest: | |
assignee: | nobody → Sridhar Gaddam (sridhargaddam) |
Changed in neutron: | |
status: | In Progress → Incomplete |
assignee: | Sridhar Gaddam (sridhargaddam) → nobody |
@Matt, if you plan to submit a patch please feel free to proceed. Otherwise, I'll look into this issue tomm'. Thanks.