Difference between revisions of "ThirdPartySystems/Quobyte CI"

Revision as of 08:06, 22 July 2016

**3rd party system:** Quobyte CI
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

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

Manila CI is currently unable to run checks due to a DevStack/Neutron change that changes DevStack default behaviour. We're working on an updated configuration.
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.

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)

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.

@@ Line 25: / Line 25: @@
 ==== Bugs/changes affecting the Manila CI results: ====
+* Manila CI is currently unable to run checks due to a [https://review.openstack.org/#/c/343072/ DevStack/Neutron change] that changes DevStack default behaviour. We're working on an updated configuration.
 * 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.
+* 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.