Inconsistent Neutron deployments
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tripleo |
Expired
|
Undecided
|
Unassigned |
Bug Description
At the moment I'm not sure if this is an upstream/downstream issue so I'm filing it here, let me know if I should move it.
Description
=======
I run automated performance tests on builds coming down the RDO pipeline. Recently some deployments of the same hash have terrible Neutron performance. If you follow the link and click through to Kibana you can see one example.
If you scroll down until you see errors for various neutron tests and look at the raw result distribution normal neutron API actions like create-
After redeploying the same RDO hash (the results on the top) performance is a much more normal distribution.
http://
If this where a single event I would ignore it, but it's happened several times now, were it across multiple versions I would attribute it to some environmental conditions, but that's not the case either it's Ocata only.
dlrn_hash: 19e86b3bef7164e
http://
dlrn_hash: dd2065a3901cbe2
http://
dlrn_hash: 7c30084d848bb45
http://
dlrn_hash: bdc175be2665558
http://
dlrn_hash: 2bf63a3ea2cd6ce
http://
Steps to reproduce
=======
Deploy the latest drln hash from the RDO pipeline on baremetal and begin
creating/deleting several hundred neutron objects. Repeat until whatever
magic causes this bug triggers.
Expected Result
=======
Neutron works as expected under load
Actual Result
=======
Neutron is non-functional for non-trivial workloads
Changed in tripleo: | |
status: | New → Triaged |
importance: | Undecided → Medium |
milestone: | none → pike-3 |
Changed in tripleo: | |
milestone: | pike-3 → pike-rc1 |
Changed in tripleo: | |
milestone: | pike-rc1 → queens-1 |
Changed in tripleo: | |
milestone: | queens-1 → queens-2 |
Changed in tripleo: | |
milestone: | queens-2 → queens-3 |
Changed in tripleo: | |
milestone: | queens-3 → queens-rc1 |
Changed in tripleo: | |
milestone: | queens-rc1 → rocky-1 |
Changed in tripleo: | |
milestone: | rocky-1 → rocky-2 |
Changed in tripleo: | |
milestone: | rocky-2 → rocky-3 |
Changed in tripleo: | |
milestone: | rocky-3 → rocky-rc1 |
Changed in tripleo: | |
milestone: | rocky-rc1 → stein-1 |
Changed in tripleo: | |
milestone: | stein-1 → stein-2 |
This is an automated cleanup. This bug report has been closed because it
is older than 18 months and there is no open code change to fix this.
After this time it is unlikely that the circumstances which lead to
the observed issue can be reproduced.
If you can reproduce the bug, please:
* reopen the bug report (set to status "New")
* AND add the detailed steps to reproduce the issue (if applicable)
* AND leave a comment "CONFIRMED FOR: <RELEASE_NAME>"
Only still supported release names are valid (FUTURE, PIKE, QUEENS, ROCKY, STEIN).
Valid example: CONFIRMED FOR: FUTURE