Difference between revisions of "ThirdPartySystems/Quobyte CI"
(Updated overall CI issues) |
(Updated CI states. Cinder based CIs no longer fail, Manila CI fix is waiting for release & roll out.) |
||
| Line 15: | Line 15: | ||
* 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 randomly hits bug [https://bugs.launchpad.net/nova/+bug/1606136 #1606136] | * Cinder CI randomly hits bug [https://bugs.launchpad.net/nova/+bug/1606136 #1606136] | ||
| − | |||
==== 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] | ||
| − | |||
==== 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] | ||
| − | |||
==== Bugs/changes affecting the Manila CI results: ==== | ==== 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 skips several groups of non-implemented Manila feature test groups (snapshots, etc.) based on the Manila tempest tests config parameters. | ||
* Manila CI produces random false negatives due to [https://bugs.launchpad.net/manila/+bug/1560345 bug #1560345]. A driver update to remedy this is in preparation at [https://review.openstack.org/#/c/345219/ change #345219]. | * Manila CI produces random false negatives due to [https://bugs.launchpad.net/manila/+bug/1560345 bug #1560345]. A driver update to remedy this is in preparation at [https://review.openstack.org/#/c/345219/ change #345219]. | ||
| − | * Manila CI currently hits a Quobyte 1.3 downward compatibility bug, we're working on fixing this and updating the CI system | + | * Manila CI currently hits a Quobyte 1.3 downward compatibility bug, we're working on fixing this and updating the CI system. A bugfix has been implemented and will be rolled out as soon as Quobyte 1.3.1 has been releases (expected in the next 48hrs). |
Revision as of 06:23, 15 August 2016
| 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 (stable), 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 randomly hits bug #1606136
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
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
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 produces random false negatives due to bug #1560345. A driver update to remedy this is in preparation at change #345219.
- Manila CI currently hits a Quobyte 1.3 downward compatibility bug, we're working on fixing this and updating the CI system. A bugfix has been implemented and will be rolled out as soon as Quobyte 1.3.1 has been releases (expected in the next 48hrs).
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.
