Jump to: navigation, search

Difference between revisions of "ThirdPartySystems/Quobyte CI"

(Updated CI status, new bugs are hitting us)
(Update Cinder related CI status reports.)
Line 19: Line 19:
 
* Cinder CI explicitly skips test_boot_server_from_encrypted_volume_luks until bug [https://bugs.launchpad.net/tempest/+bug/1702843 #1702843] is fixed.
 
* Cinder CI explicitly skips test_boot_server_from_encrypted_volume_luks until bug [https://bugs.launchpad.net/tempest/+bug/1702843 #1702843] is fixed.
 
* Cinder CI explicitly skips test_snapshot_backup until bug [https://bugs.launchpad.net/cinder/+bug/1703405 #1703405] is fixed.
 
* Cinder CI explicitly skips test_snapshot_backup until bug [https://bugs.launchpad.net/cinder/+bug/1703405 #1703405] is fixed.
* Cinder CI is affected by bug [https://bugs.launchpad.net/nova/+bug/1700583 1700583], we're investigating a solution for this.
+
* Cinder CI is pinning the DevStack version to commit 0d9c896 until bug [https://bugs.launchpad.net/nova/+bug/1700583 1700583] is fixed.
  
 
==== Bugs/changes affecting the OS-Brick CI results: ====
 
==== Bugs/changes affecting the OS-Brick CI results: ====
Line 25: Line 25:
 
* 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 explicitely skips test_boot_server_from_encrypted_volume_luks until bug [https://bugs.launchpad.net/tempest/+bug/1702843 #1702843] is fixed.
 
* OS-Brick CI explicitely skips test_boot_server_from_encrypted_volume_luks until bug [https://bugs.launchpad.net/tempest/+bug/1702843 #1702843] is fixed.
* OS-Brick CI is affected by bug [https://bugs.launchpad.net/nova/+bug/1700583 1700583], we're investigating a solution for this.
+
* OS-Brick CI is pinning the DevStack version to commit 0d9c896 until bug [https://bugs.launchpad.net/nova/+bug/1700583 1700583] is fixed.
  
 
==== Bugs/changes affecting the Nova CI results: ====
 
==== Bugs/changes affecting the Nova CI results: ====
Line 31: Line 31:
 
* 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 explicitely skips test_boot_server_from_encrypted_volume_luks until bug [https://bugs.launchpad.net/tempest/+bug/1702843 #1702843] is fixed.
 
* Nova CI explicitely skips test_boot_server_from_encrypted_volume_luks until bug [https://bugs.launchpad.net/tempest/+bug/1702843 #1702843] is fixed.
* Nova CI is affected by bug [https://bugs.launchpad.net/nova/+bug/1700583 1700583], we're investigating a solution for this.
+
* Nova CI is pinning the DevStack version to commit 0d9c896 until bug [https://bugs.launchpad.net/nova/+bug/1700583 1700583] is fixed.
  
 
==== Bugs/changes affecting the Manila CI results: ====
 
==== Bugs/changes affecting the Manila CI results: ====

Revision as of 10:32, 3 August 2017

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


Status Details

Reporting in Cinder project (stable), OS-Brick project (stable), Manila project (stable), and Nova project (stable)

Currently all CIs are providing false negative results. The Manila CI has a configuration deprecation issue while the Cinder based CIs are failing tests since last night. We're analyzing the issues and working on their correction.

Bugs/changes affecting the Cinder CI results:

  • Cinder CI explicitly skips encrypted volume test as proposed on the mailing list, affects 1 test.
  • Cinder CI runs with basic apparmor protection as a workaround for a libvirt apparmor config issue until that bug is solved
  • Cinder CI randomly hits bug #1606136
  • Cinder CI explicitly skips test_boot_server_from_encrypted_volume_luks until bug #1702843 is fixed.
  • Cinder CI explicitly skips test_snapshot_backup until bug #1703405 is fixed.
  • Cinder CI is pinning the DevStack version to commit 0d9c896 until bug 1700583 is fixed.

Bugs/changes affecting the OS-Brick CI results:

  • OS-Brick CI runs with basic apparmor protection as a workaround for a libvirt apparmor config issue until that bug is solved
  • OS-Brick CI randomly hits bug #1606136
  • OS-Brick CI explicitely skips test_boot_server_from_encrypted_volume_luks until bug #1702843 is fixed.
  • OS-Brick CI is pinning the DevStack version to commit 0d9c896 until bug 1700583 is fixed.

Bugs/changes affecting the Nova CI results:

  • Nova CI runs with basic apparmor protection as a workaround for a libvirt apparmor config issue until that bug is solved
  • Nova CI randomly hits bug #1606136
  • Nova CI explicitely skips test_boot_server_from_encrypted_volume_luks until bug #1702843 is fixed.
  • Nova CI is pinning the DevStack version to commit 0d9c896 until bug 1700583 is fixed.

Bugs/changes affecting the Manila CI results:

  • Manila CI runs all basic tests as well as some optional tempest test groups:
    • run_quota_tests=True
    • run_extend_tests=True
    • run_shrink_tests=True
  • Manila CI is currently affected by a backend API incompatibility. We're working on fixing this in the backend.

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.