Since the migration to new engine facade, some operations that shouldn't be executing within a txn, are logging a "session semantic violated" warning
Bug #1924789 reported by
Rodolfo Alonso
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
neutron |
Confirmed
|
High
|
Unassigned |
Bug Description
When Neutron moved to the new engine facade, some operations that could not be executed inside a running transaction, are allowed as an exception. Those commands are executed disabling first the transaction guard. Example:
if context.
There are three occurrences in the code, all of them in the neutron.db.l3_db code, all of them creating/deleting a port from a router.
Snippet: paste.openstack
Changed in neutron: | |
importance: | Medium → High |
To post a comment you must log in.
Hi Rodolfo,
As I read that code this does not break the relevant operations, it only prints noisy warnings. Both the operation exempting itself from the transaction guard and the noisy warning look completely intentional. Do you want to selectively suppress the warning where we had the transaction guard hack? To me that makes perfect sense.
Cheers,
Bence