Big Switch: hash shouldn't be updated on unsuccessful calls
Bug #1348766 reported by
Kevin Benton
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
neutron |
Fix Released
|
Medium
|
Kevin Benton | ||
Icehouse |
Fix Released
|
Medium
|
Kevin Benton |
Bug Description
The configuration hash db is updated on every response from the backend including errors that contain an empty hash. This is causing the hash to be wiped out if a standby controller is contacted first, which opens a narrow time window where the backend could become out of sync. It should only update the hash on successful REST calls.
description: | updated |
description: | updated |
Changed in neutron: | |
assignee: | nobody → Kevin Benton (kevinbenton) |
tags: | added: bigswitch |
Changed in neutron: | |
importance: | Undecided → Medium |
Changed in neutron: | |
milestone: | none → juno-3 |
Changed in neutron: | |
status: | Fix Committed → Fix Released |
Changed in neutron: | |
milestone: | juno-3 → 2014.2 |
To post a comment you must log in.
Fix proposed to branch: master /review. openstack. org/109695
Review: https:/