BigSwitch plugin generates unnecessary errors on 404 from controller
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
neutron |
Fix Released
|
Medium
|
Kevin Benton | ||
Grizzly |
Fix Released
|
Medium
|
Gary Kotton |
Bug Description
There are certain times when a 404 error from the backend controller can be safely ignored.
For example, on the _unplug_interface call, remote rest exceptions aren't raised any further because they are expected to generate 404 errors if the network has already been deleted.
https:/
Even though these are ignored by not raising the exception further, it causes errors in the logs and marks a controller as failed, causing the failover logic to send the same request to every backend controller until they are all marked as failed, ultimately generating even more errors.
This condition is exacerbated by bug 1197627, which is a race condition that frequently causes double port delete and unplug requests.
Changed in neutron: | |
assignee: | nobody → Kevin Benton (blak111) |
Changed in neutron: | |
importance: | Undecided → Medium |
milestone: | none → havana-2 |
tags: | added: bigswitch |
tags: | added: grizzly-backport-potential |
Changed in neutron: | |
status: | Fix Committed → Fix Released |
tags: | removed: grizzly-backport-potential in-stable-grizzly |
Changed in neutron: | |
milestone: | havana-2 → 2013.2 |
Fix proposed to branch: master /review. openstack. org/36586
Review: https:/