Difference between revisions of "ThirdPartySystems/Quobyte CI"
(Updated overall CI status on nova related CIs, updated recheck section.) |
(updated apparmor config hints) |
||
Line 9: | Line 9: | ||
=== Status Details === | === Status Details === | ||
− | Reporting in Cinder project (stable), OS-Brick project (stable), Manila project ( | + | Reporting in Cinder project (stable), OS-Brick project (stable), Manila project (unstable), and Nova project (stable) |
==== Bugs/changes affecting the Cinder CI results: ==== | ==== Bugs/changes affecting the Cinder CI results: ==== | ||
* Cinder CI explicitely skips encrypted volume test as proposed on [http://lists.openstack.org/pipermail/openstack-dev/2015-July/069099.html the mailing list], affects 1 test. | * Cinder CI explicitely skips encrypted volume test as proposed on [http://lists.openstack.org/pipermail/openstack-dev/2015-July/069099.html the mailing list], affects 1 test. | ||
− | * Cinder CI runs | + | * Cinder CI runs with basic apparmor protection as a workaround for [https://bugs.launchpad.net/nova/+bug/1598833 #1598833] until that bug is solved |
* Cinder CI uses nova patch [https://review.openstack.org/#/c/337174/1 #337174] due to [https://bugs.launchpad.net/nova/+bug/1597644 bug #1597644] until that Nova bug has been solved | * Cinder CI uses nova patch [https://review.openstack.org/#/c/337174/1 #337174] due to [https://bugs.launchpad.net/nova/+bug/1597644 bug #1597644] until that Nova bug has been solved | ||
==== Bugs/changes affecting the OS-Brick CI results: ==== | ==== Bugs/changes affecting the OS-Brick CI results: ==== | ||
− | * OS-Brick CI runs | + | * OS-Brick CI runs with basic apparmor protection as a workaround for [https://bugs.launchpad.net/nova/+bug/1598833 #1598833] until that bug is solved |
* OS-Brick CI uses nova patch [https://review.openstack.org/#/c/337174/1 #337174] due to [https://bugs.launchpad.net/nova/+bug/1597644 bug #1597644] until that Nova bug has been solved | * OS-Brick CI uses nova patch [https://review.openstack.org/#/c/337174/1 #337174] due to [https://bugs.launchpad.net/nova/+bug/1597644 bug #1597644] until that Nova bug has been solved | ||
==== Bugs/changes affecting the Nova CI results: ==== | ==== Bugs/changes affecting the Nova CI results: ==== | ||
* Nova CI is affected by a permission bug introduced by [https://github.com/openstack/nova/commit/ea3904b168e4360b6c68464dbcd0585987b27e91 Change-Id: Ia84579b84105e8ad6146591188a96e847e762c77] monitored in [https://bugs.launchpad.net/nova/+bug/1597644 bug #1597644] . Revert patch is in review at [https://review.openstack.org/#/c/337174/1 change #337174] ('''reviewers welcome!!!''') | * Nova CI is affected by a permission bug introduced by [https://github.com/openstack/nova/commit/ea3904b168e4360b6c68464dbcd0585987b27e91 Change-Id: Ia84579b84105e8ad6146591188a96e847e762c77] monitored in [https://bugs.launchpad.net/nova/+bug/1597644 bug #1597644] . Revert patch is in review at [https://review.openstack.org/#/c/337174/1 change #337174] ('''reviewers welcome!!!''') | ||
− | * Nova CI runs | + | * Nova CI runs with basic apparmor protection as a workaround for [https://bugs.launchpad.net/nova/+bug/1598833 #1598833] until that bug is solved |
==== Bugs/changes affecting the Manila CI results: ==== | ==== Bugs/changes affecting the Manila CI results: ==== | ||
− | * CI skips several groups of non-implemented Manila feature test groups (snapshots, etc.) based on the Manila tempest tests config parameters. | + | * Manila CI skips several groups of non-implemented Manila feature test groups (snapshots, etc.) based on the Manila tempest tests config parameters. |
+ | * Manila CI is currently unstable du to a range of connectivity and stability issues. We're investigating into the details in order to correct this. | ||
Revision as of 12:34, 18 July 2016
Gerrit Account: quobyteci | |
Contact Information: silvan@quobyte.com (kaisers@IRC), robert@quobyte.com (mrlarkin@IRC), felix@quobyte.com, bjoern@quobyte.com, | |
Intent: Test Cinder, OS-Brick, Manila, and Nova changes against Quobyte drivers | |
Structure: ansible installed sos-ci setup with some modifications | |
Method: sos-ci monitors Gerrit event stream and triggers test builds, ansible based installation in DevStack instances, running volume related tempest tests vs. Cinder, OS-Brick, and Nova changes. Similar installation testing manila changes with their respective tempest tests on a quobyte backend based setup. | |
OpenStack Programs: Cinder, OS-Brick, Manila, and Nova | |
Current Status: enabled |
Contents
Status Details
Reporting in Cinder project (stable), OS-Brick project (stable), Manila project (unstable), and Nova project (stable)
Bugs/changes affecting the Cinder CI results:
- Cinder CI explicitely skips encrypted volume test as proposed on the mailing list, affects 1 test.
- Cinder CI runs with basic apparmor protection as a workaround for #1598833 until that bug is solved
- Cinder CI uses nova patch #337174 due to bug #1597644 until that Nova bug has been solved
Bugs/changes affecting the OS-Brick CI results:
- OS-Brick CI runs with basic apparmor protection as a workaround for #1598833 until that bug is solved
- OS-Brick CI uses nova patch #337174 due to bug #1597644 until that Nova bug has been solved
Bugs/changes affecting the Nova CI results:
- Nova CI is affected by a permission bug introduced by Change-Id: Ia84579b84105e8ad6146591188a96e847e762c77 monitored in bug #1597644 . Revert patch is in review at change #337174 (reviewers welcome!!!)
- Nova CI runs with basic apparmor protection as a workaround for #1598833 until that bug is solved
Bugs/changes affecting the Manila CI results:
- Manila CI skips several groups of non-implemented Manila feature test groups (snapshots, etc.) based on the Manila tempest tests config parameters.
- Manila CI is currently unstable du to a range of connectivity and stability issues. We're investigating into the details in order to correct this.
Rechecking Quobyte CI Systems
Quobyte CI systems trigger rechecks in two scenarios:
- Jenkins recheck: Every time Jenkins comments +1 on a change the corresponding Quobyte CI is triggered. This includes initial check runs as well as recheck triggered Jenkins re-runs
- CI specific recheck (see below)
Quobyte CI Specific Rechecks
All CI systems run by Quobyte support rechecking by adding the comment 'run <ci-instance-name>' to the patch set in question.
Recheck trigger: "run <ci-instance-name>"
For example:
run cinder-quobyteci-dsvm-volume
This command works even if there's no previous report from the given CI instance for the given patch set.