Jump to: navigation, search

Difference between revisions of "ThirdPartySystems/Quobyte CI"

(Updating page structure)
(Manila CI is up, also adds link to xenial support drop change.)
(67 intermediate revisions by the same user not shown)
Line 1: Line 1:
 
{{ThirdPartySystemInfo|name=Quobyte CI
 
{{ThirdPartySystemInfo|name=Quobyte CI
 
|account=quobyteci
 
|account=quobyteci
|contact= silvan@quobyte.com (kaisers@IRC), robert@quobyte.com (mrlarkin@IRC), felix@quobyte.com, bjoern@quobyte.com,
+
|contact= 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
 
|intent=Test Cinder, OS-Brick, Manila, and Nova changes against [[Quobyte]] drivers
 
|structure=ansible installed [https://github.com/j-griffith/sos-ci sos-ci] setup with some  [https://github.com/casusbelli/sos-ci modifications]
 
|structure=ansible installed [https://github.com/j-griffith/sos-ci sos-ci] setup with some  [https://github.com/casusbelli/sos-ci modifications]
Line 10: Line 10:
 
=== Status Details ===
 
=== Status Details ===
 
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)
<br>
 
Bugs/changes affecting the Cinder CI results:
 
* Currently affected by a bug related to online snapshot test test_snapshot_create_with_volume_in_use, details at [https://bugs.launchpad.net/nova/+bug/1598833 #1598833]
 
** Error reason is partially hidden in Nova logs by [https://bugs.launchpad.net/nova/+bug/1168011 #1168011].
 
* Currently affected by a permission issue introduced by [https://github.com/openstack/nova/commit/ea3904b168e4360b6c68464dbcd0585987b27e91 Change-Id: Ia84579b84105e8ad6146591188a96e847e762c77] monitored in [https://bugs.launchpad.net/nova/+bug/1597644 bug #1597644]
 
* CI explicitely skips encrypted volume test as proposed on [http://lists.openstack.org/pipermail/openstack-dev/2015-July/069099.html the mailing list], affects 1 test.
 
<br>
 
Bugs/changes affecting the OS-Brick CI results:
 
* Currently affected by the same bugs as the Cinder CI (see above).
 
* OS-Brick CI is is reporting
 
<br>
 
Bugs/changes affecting the Nova CI results:
 
* Currently affected by the same bugs as the Cinder CI (see above).
 
* Nova CI is reporting
 
<br>
 
Bugs/changes affecting the Manila CI results:
 
* CI skips several groups of non-implemented Manila feature test groups (snapshots, etc.) based on the Manila tempest tests config parameters.
 
  
 +
==== 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: ====
 +
* 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 explicitly skips test_snapshot_backup until bug [https://bugs.launchpad.net/cinder/+bug/1703405 #1703405] is fixed.
  
=== Rechecking Quobyte CI Systems ===
+
==== 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 randomly hits bug [https://bugs.launchpad.net/nova/+bug/1606136 #1606136]
  
'''Recheck trigger:''' "run <ci-instance-name>"
+
==== 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 randomly hits bug [https://bugs.launchpad.net/nova/+bug/1606136 #1606136]
  
All CI systems run by Quobyte support rechecking by adding the comment 'run <ci-instance-name>' to the patch set in question.
+
==== Bugs/changes affecting the Manila CI results: ====
For example:  
+
* 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
  
<nowiki>
+
=== Rechecking Quobyte CI Systems ===
    run cinder-quobyteci-dsvm-volume
+
Quobyte CI systems trigger rechecks in two scenarios:
</nowiki>
+
* 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)
  
This command works even if there's no previous report from the given CI instance for the given patch set.
+
==== 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.
 +
<br>
 +
'''Recheck trigger:''' "run-Quobyte CI"
 +
<br>
 +
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.

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.