Difference between revisions of "ThirdPartySystems/Quobyte CI"
(Updates overall CI status) |
(Updated overall CI status) |
||
| Line 6: | Line 6: | ||
|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. | |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. | ||
|programs=Cinder, OS-Brick, Manila, and Nova | |programs=Cinder, OS-Brick, Manila, and Nova | ||
| − | |status= | + | |status=enabled}} |
=== Status Details === | === 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: ==== | ==== 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 with basic apparmor protection as a workaround for [https://bugs.launchpad.net/nova/+bug/1598833 #1598833] until that bug is solved | * 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 | + | * Cinder CI continuously hits a bug with attaching/detaching images, we're investigating this. |
| − | |||
| − | |||
==== Bugs/changes affecting the OS-Brick CI results: ==== | ==== Bugs/changes affecting the OS-Brick CI results: ==== | ||
* 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 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 randomly hits bug [https://bugs.launchpad.net/nova/+bug/1606136 #1606136] | * OS-Brick CI randomly hits bug [https://bugs.launchpad.net/nova/+bug/1606136 #1606136] | ||
| − | * OS-Brick CI | + | * OS-Brick CI continuously hits a bug with attaching/detaching images, we're investigating this. |
==== Bugs/changes affecting the Nova CI results: ==== | ==== Bugs/changes affecting the Nova CI results: ==== | ||
* Nova CI runs with basic apparmor protection as a workaround for [https://bugs.launchpad.net/nova/+bug/1598833 #1598833] until that bug is solved | * Nova CI runs with basic apparmor protection as a workaround for [https://bugs.launchpad.net/nova/+bug/1598833 #1598833] until that bug is solved | ||
* Nova CI randomly hits bug [https://bugs.launchpad.net/nova/+bug/1606136 #1606136] | * Nova CI randomly hits bug [https://bugs.launchpad.net/nova/+bug/1606136 #1606136] | ||
| − | * Nova CI | + | * Nova CI continuously hits a bug with attaching/detaching images, we're investigating this. |
==== Bugs/changes affecting the Manila CI results: ==== | ==== Bugs/changes affecting the Manila CI results: ==== | ||
Revision as of 09:40, 12 January 2017
| Gerrit Account: quobyteci | |
| Contact Information: primary contact: silvan@quobyte.com (kaisers@IRC); backup contacts (in order): 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 continuously hits a bug with attaching/detaching images, we're investigating this.
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 randomly hits bug #1606136
- OS-Brick CI continuously hits a bug with attaching/detaching images, we're investigating this.
Bugs/changes affecting the Nova CI results:
- Nova CI runs with basic apparmor protection as a workaround for #1598833 until that bug is solved
- Nova CI randomly hits bug #1606136
- Nova CI continuously hits a bug with attaching/detaching images, we're investigating this.
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 down for reconfiguration
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.
