Jump to: navigation, search

Difference between revisions of "ThirdPartySystems/Quobyte CI"

(Update Cinder related CI status reports.)
(Manila CI is up, also adds link to xenial support drop change.)
 
(31 intermediate revisions by the same user not shown)
Line 11: Line 11:
 
Reporting in Cinder project (stable), OS-Brick project (stable), Manila project (stable), and Nova project (stable)
 
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 all CI results: ====
 +
* Manila CI is up & running
 +
* All other CIs currently produce static negatives due to devstack [https://github.com/openstack/devstack/commit/2e6677869925c86c01cae883b3dde6cccad81d30 Xenial support removal],  we're working to fix this issue.
  
 
==== Bugs/changes affecting the Cinder CI results: ====
 
==== Bugs/changes affecting the Cinder CI results: ====
* Cinder CI explicitly 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://bugzilla.redhat.com/show_bug.cgi?id=1361592 a libvirt apparmor config issue] until that bug is solved
 
* Cinder CI runs with basic apparmor protection as a workaround for [https://bugzilla.redhat.com/show_bug.cgi?id=1361592 a libvirt apparmor config issue] 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]
* 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 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: ====
 
* OS-Brick CI runs with basic apparmor protection as a workaround for [https://bugzilla.redhat.com/show_bug.cgi?id=1361592 a libvirt apparmor config issue] until that bug is solved
 
* OS-Brick CI runs with basic apparmor protection as a workaround for [https://bugzilla.redhat.com/show_bug.cgi?id=1361592 a libvirt apparmor config issue] 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 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 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: ====
 
* Nova CI runs with basic apparmor protection as a workaround for [https://bugzilla.redhat.com/show_bug.cgi?id=1361592 a libvirt apparmor config issue] until that bug is solved
 
* Nova CI runs with basic apparmor protection as a workaround for [https://bugzilla.redhat.com/show_bug.cgi?id=1361592 a libvirt apparmor config issue] 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 explicitely skips test_boot_server_from_encrypted_volume_luks until bug [https://bugs.launchpad.net/tempest/+bug/1702843 #1702843] is fixed.
 
* 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: ====
Line 38: Line 33:
 
** run_extend_tests=True
 
** run_extend_tests=True
 
** run_shrink_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 ===
 
=== Rechecking Quobyte CI Systems ===
Line 46: Line 40:
  
 
==== Quobyte CI Specific Rechecks ====
 
==== 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.
+
All CI systems run by Quobyte support rechecking by adding the comment 'run-Quobyte CI' to the patch set in question.
 
<br>
 
<br>
 
+
'''Recheck trigger:''' "run-Quobyte CI"
'''Recheck trigger:''' "run <ci-instance-name>"
 
 
<br>
 
<br>
 
+
An older recheck trigger including the Quobyte CI instance name is outdated now and now longer used.
For example:
+
The recheck command works even if there's no previous report from the given CI instance for the given patch set.
 
 
<nowiki>
 
    run cinder-quobyteci-dsvm-volume
 
</nowiki>
 
 
 
This command works even if there's no previous report from the given CI instance for the given patch set.
 

Latest revision as of 11:29, 11 December 2019

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)

Bugs/changes affecting all CI results:

  • Manila CI is up & running
  • All other CIs currently produce static negatives due to devstack Xenial support removal, we're working to fix this issue.

Bugs/changes affecting the Cinder CI results:

  • 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_snapshot_backup until bug #1703405 is fixed.

Bugs/changes affecting the OS-Brick CI results:

Bugs/changes affecting the Nova CI results:

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

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-Quobyte CI' to the patch set in question.
Recheck trigger: "run-Quobyte CI"
An older recheck trigger including the Quobyte CI instance name is outdated now and now longer used. The recheck command works even if there's no previous report from the given CI instance for the given patch set.