yahoo-eng-team team mailing list archive

[Kevin Benton <1348766@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

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.

** Affects: neutron
     Importance: Undecided
     Assignee: Kevin Benton (kevinbenton)
         Status: New

** Description changed:

  The configuration hash db is updated on every response from the backend
- including errors that contain an empty hash. It should only update the
- hash on successful REST calls.
+ including errors that contain an empty hash. This is causing the hash to
+ be wiped out if a standby controller is contacted first. It should only
+ update the hash on successful REST calls.

** Description changed:

  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. It should only
- update the hash on successful REST calls.
+ 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.

** Changed in: neutron
     Assignee: (unassigned) => Kevin Benton (kevinbenton)

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1348766

Title:
  Big Switch: hash shouldn't be updated on unsuccessful calls

Status in OpenStack Neutron (virtual network service):
  New

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.

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1348766/+subscriptions