Jump to: navigation, search

Difference between revisions of "ThirdPartySystems/Quobyte CI"

(Fix for Cannot send request Bug in Manila CI has been merged, removing bug info here.)
(Updated CI system status)
Line 9: Line 9:
  
 
=== Status Details ===
 
=== Status Details ===
Reporting in Cinder project (stable), OS-Brick project (stable), Manila project (stable), and Nova project (stable)
+
Reporting in Cinder project (unstable), OS-Brick project (unstable), Manila project (unstable), and Nova project (unstable)
  
 
==== Bugs/changes affecting the Cinder CI results: ====
 
==== Bugs/changes affecting the Cinder CI results: ====
Line 15: Line 15:
 
* Cinder CI runs with basic apparmor protection as a workaround for [https://bugs.launchpad.net/nova/+bug/1598833 #1598833] until that bug is solved
 
* Cinder CI runs with basic apparmor protection as a workaround for [https://bugs.launchpad.net/nova/+bug/1598833 #1598833] 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 is currently affected by a private cloud issue, we're debugging this
  
 
==== 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://bugs.launchpad.net/nova/+bug/1598833 #1598833] until that bug is solved
 
* OS-Brick CI runs with basic apparmor protection as a workaround for [https://bugs.launchpad.net/nova/+bug/1598833 #1598833] 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 is currently affected by a private cloud issue, we're debugging this
  
 
==== 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://bugs.launchpad.net/nova/+bug/1598833 #1598833] until that bug is solved
 
* Nova CI runs with basic apparmor protection as a workaround for [https://bugs.launchpad.net/nova/+bug/1598833 #1598833] 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 is currently affected by a private cloud issue, we're debugging this
  
 
==== Bugs/changes affecting the Manila CI results: ====
 
==== Bugs/changes affecting the Manila CI results: ====
 
* Manila CI skips several groups of non-implemented Manila feature test groups (snapshots, etc.) based on the Manila tempest tests config parameters.
 
* Manila CI skips several groups of non-implemented Manila feature test groups (snapshots, etc.) based on the Manila tempest tests config parameters.
* Manila CI currently hits a Quobyte 1.3 downward compatibility bug, we're working on fixing this and updating the CI system. A bugfix has been implemented and will be rolled out as soon as Quobyte 1.3.1 has been releases (expected in the next 48hrs).
+
* Manila CI is currently unstable due to configuration changes, we're debugging this
  
  

Revision as of 08:57, 6 October 2016

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 (unstable), OS-Brick project (unstable), Manila project (unstable), and Nova project (unstable)

Bugs/changes affecting the Cinder CI results:

  • Cinder CI explicitely skips encrypted volume test as proposed on the mailing list, affects 1 test.
  • Cinder CI runs with basic apparmor protection as a workaround for #1598833 until that bug is solved
  • Cinder CI randomly hits bug #1606136
  • Cinder CI is currently affected by a private cloud issue, we're debugging this

Bugs/changes affecting the OS-Brick CI results:

  • OS-Brick CI runs with basic apparmor protection as a workaround for #1598833 until that bug is solved
  • OS-Brick CI randomly hits bug #1606136
  • OS-Brick CI is currently affected by a private cloud issue, we're debugging this

Bugs/changes affecting the Nova CI results:

  • Nova CI runs with basic apparmor protection as a workaround for #1598833 until that bug is solved
  • Nova CI randomly hits bug #1606136
  • Nova CI is currently affected by a private cloud issue, we're debugging this

Bugs/changes affecting the Manila CI results:

  • 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 due to configuration changes, we're debugging this


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.