ThirdPartySystems/Quobyte CI

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

Bugs/changes affecting all CI results:

 * None

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.
 * Cinder CI explicitly skips test_snapshot_create_delete_with_volume_in_use and test_snapshot_create_offline_delete_online until bug #1716920 is fixed.
 * Cinder CI explicitly skips test_backup_create_attached_volume until bug #1744692 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_snapshot_create_delete_with_volume_in_use and test_snapshot_create_offline_delete_online until bug #1716920 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_snapshot_create_delete_with_volume_in_use and test_snapshot_create_offline_delete_online until bug #1716920 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

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.