yahoo-eng-team team mailing list archive

[Brian Haley <1716522@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

Recently saw this error in the dvr-multinode grenade job:

ERROR neutron.api.v2.resource [None req-efa49ab7-5bc4-49a4-9ede-e6f638f80004 admin admin] remove_router_interface failed: No details.: StaleDataError: DELETE statement on table 'standardattributes' expected to delete 1 row(s); 0 were matched.  Please set confirm_deleted_rows=False within the mapper configuration to prevent this warning.
[...]
INFO neutron.wsgi [None req-efa49ab7-5bc4-49a4-9ede-e6f638f80004 admin admin] 10.210.34.251 "PUT /v2.0/routers/12dd139f-6d5f-437d-87bf-a75b6edf5125/remove_router_interface HTTP/1.1" status: 500  len: 363 time: 47.3295698

http://logs.openstack.org/43/500143/4/check/gate-grenade-dsvm-neutron-
dvr-multinode-ubuntu-xenial-
nv/710e31d/logs/screen-q-svc.txt.gz#_Sep_11_19_16_23_495551

I won't cut-paste the long backtrace.

Kevin Benton looked and found the ML2 agent code on both agents was
updating the port status once it received an update from the server,
regardless if that status had changed, most likely triggering this error
and filling both the q-agt and q-svc logs with lots of messages.

https://review.openstack.org/#/c/502850/ test patch started.

** Affects: neutron
     Importance: High
         Status: Confirmed

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

Title:
  StaleDataError deleting router interface

Status in neutron:
  Confirmed

Bug description:
  Recently saw this error in the dvr-multinode grenade job:

  ERROR neutron.api.v2.resource [None req-efa49ab7-5bc4-49a4-9ede-e6f638f80004 admin admin] remove_router_interface failed: No details.: StaleDataError: DELETE statement on table 'standardattributes' expected to delete 1 row(s); 0 were matched.  Please set confirm_deleted_rows=False within the mapper configuration to prevent this warning.
  [...]
  INFO neutron.wsgi [None req-efa49ab7-5bc4-49a4-9ede-e6f638f80004 admin admin] 10.210.34.251 "PUT /v2.0/routers/12dd139f-6d5f-437d-87bf-a75b6edf5125/remove_router_interface HTTP/1.1" status: 500  len: 363 time: 47.3295698

  http://logs.openstack.org/43/500143/4/check/gate-grenade-dsvm-neutron-
  dvr-multinode-ubuntu-xenial-
  nv/710e31d/logs/screen-q-svc.txt.gz#_Sep_11_19_16_23_495551

  I won't cut-paste the long backtrace.

  Kevin Benton looked and found the ML2 agent code on both agents was
  updating the port status once it received an update from the server,
  regardless if that status had changed, most likely triggering this
  error and filling both the q-agt and q-svc logs with lots of messages.

  https://review.openstack.org/#/c/502850/ test patch started.

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