yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #18739
[Bug 1354072] [NEW] Transaction is not rollbacked properly in bind_router
Public bug reported:
This stracktrace has been observed:
http://logs.openstack.org/29/112229/5/gate/gate-tempest-dsvm-neutron-
pg/db8ad58/logs/screen-q-svc.txt.gz?level=TRACE#_2014-08-07_15_49_00_061
Since change:
https://review.openstack.org/#/c/73234/
A unique constraint has been introduced. This prevents the race
condition to cause multiple entries in the table, however concurrent
changes can still occur, hence the DBDuplicateEntry can still occur.
That said, it looks like the transaction is not cleaned up properly.
** Affects: neutron
Importance: Undecided
Assignee: Armando Migliaccio (armando-migliaccio)
Status: New
** Changed in: neutron
Assignee: (unassigned) => Armando Migliaccio (armando-migliaccio)
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1354072
Title:
Transaction is not rollbacked properly in bind_router
Status in OpenStack Neutron (virtual network service):
New
Bug description:
This stracktrace has been observed:
http://logs.openstack.org/29/112229/5/gate/gate-tempest-dsvm-neutron-
pg/db8ad58/logs/screen-q-svc.txt.gz?level=TRACE#_2014-08-07_15_49_00_061
Since change:
https://review.openstack.org/#/c/73234/
A unique constraint has been introduced. This prevents the race
condition to cause multiple entries in the table, however concurrent
changes can still occur, hence the DBDuplicateEntry can still occur.
That said, it looks like the transaction is not cleaned up properly.
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1354072/+subscriptions
Follow ups
References