[Pluggable IPAM] On request retry 'external_gateway_info' field got missed for router update case
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
neutron |
In Progress
|
Undecided
|
Carl Baldwin |
Bug Description
Issue observed on current master (should be reproducible on mitaka too).
Steps to reproduce:
1) enable pluggable ipam be setting default value for 'ipam_driver' as 'internal' in patch set, upload into gerrit
2) validate test results for gate-tempest-
3) observe that some router update related tests will fail
4) analyse screen-q-svc.txt.gz request processing to validate that after raising RetryRequest 'external_
During retrying update router request 'external_
Before retry:
{u'router': {u'external_
After retry:
{u'router': {u'name': u'tempest-
This issue is observed only on scale testing where concurent ip allocation happens for the same subnet.
Due to concurent data modifications one of the transactions is restarted by RetryRequest exception (compare-and-swap synchronization).
And for update router case restaring transaction leads to missing 'external_
Related log output:
2016-04-22 12:26:35.545 18234 DEBUG neutron.api.v2.base [req-efd63a02-
...
2016-04-22 12:26:36.873 18234 DEBUG oslo_db.api [req-efd63a02-
2016-04-22 12:26:36.874 18234 DEBUG neutron.api.v2.base [req-efd63a02-
Full log available at [1]. Trace req-efd63a02-
request processing. And [2] is failed test related to that issue.
[1] http://
[2] http://
description: | updated |
Changed in neutron: | |
assignee: | Pavel Bondar (pasha117) → Carl Baldwin (carl-baldwin) |
I want to mark this confirmed, but it needs some more info. What version of neutron? Repro steps?