Jump to: navigation, search

ThirdPartySystems/Quobyte CI

< ThirdPartySystems
Revision as of 13:32, 2 April 2015 by Kaisers (talk | contribs) (Added one more bug that is hit regularily)
3rd party system: Quobyte CI
Gerrit Account: quobyteci
Contact Information: silvan@quobyte.com, bjoern@quobyte.com, felix@quobyte.com, kaisers @ IRC
Intent: Test Cinder, Nova and Manila 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. Similar installations testing nova and manila changes with their respective tempest tests on a quobyte backend based setup. Working on openstack/nova and openstack/manila CI setups.
OpenStack Programs: Cinder, Nova, Manila
Current Status: Reporting in openstack-dev/ci-sandbox.

Currently running 304 tests, 9 skipped by tempest marked bugs, 3 - 6 failing and in debugging.
Quobyte CI is currently failing the following tests:

  • snapshot tests due to #1438603
  • test_minimum_basic_scenario and test_volume_boot_pattern due to #1249065
  • Testing currently also hits #1439634 in internal testing


Other bugs that where found by Quobyte C:

  • #1438607 - exception in cinder logging
  • #1437328 - no networks found error in tempest
  • #1434502 - Single volume assert fails in Quobyte