yahoo-eng-team team mailing list archive

[Ihar Hrachyshka <1593719@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

This error started to show up in neutron-server logs in gate after
https://review.openstack.org/#/c/328185/5 landed. The reason is that
using version_id_col makes UPDATE and DELETE filter by the revision
number, and raise StaleDataError on mismatch. That's documented in:
http://docs.sqlalchemy.org/en/latest/orm/exceptions.html#sqlalchemy.orm.exc.StaleDataError

Once the exception is raised, it's correctly caught by retry mechanism.
We should consider StateDataErrors a usual operation mode, and hence
avoid logging the exceptions in ml2 plugin. Instead, we should bubble up
exceptions to retry layer and allow it to determine if to log those
exceptions.

** Affects: neutron
     Importance: Low
         Status: New

** Changed in: neutron
   Importance: Undecided => Low

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

Title:
  StaleDataError: DELETE statement on table 'standardattributes'
  expected to delete 1 row(s); 0 were matched

Status in neutron:
  New

Bug description:
  This error started to show up in neutron-server logs in gate after
  https://review.openstack.org/#/c/328185/5 landed. The reason is that
  using version_id_col makes UPDATE and DELETE filter by the revision
  number, and raise StaleDataError on mismatch. That's documented in:
  http://docs.sqlalchemy.org/en/latest/orm/exceptions.html#sqlalchemy.orm.exc.StaleDataError

  Once the exception is raised, it's correctly caught by retry
  mechanism. We should consider StateDataErrors a usual operation mode,
  and hence avoid logging the exceptions in ml2 plugin. Instead, we
  should bubble up exceptions to retry layer and allow it to determine
  if to log those exceptions.

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