Difference between revisions of "ThirdPartySystems/Quobyte CI"
(Updated current bugs CI is hitting.) |
(Updated info on current bugs.) |
||
| Line 10: | Line 10: | ||
Quobyte CI is currently failing the following tests: | Quobyte CI is currently failing the following tests: | ||
* snapshot tests due to [https://bugs.launchpad.net/cinder/+bug/1438603 #1438603] | * snapshot tests due to [https://bugs.launchpad.net/cinder/+bug/1438603 #1438603] | ||
| − | * test_minimum_basic_scenario and test_volume_boot_pattern due to [https://bugs.launchpad.net/ | + | * test_minimum_basic_scenario and test_volume_boot_pattern and a third one due to [https://bugs.launchpad.net/tempest/+bug/1253896 #1253896] |
* seemingly random tests fail due to ResonseNotReady exceptions in test setup (and sometimes teardown) as described in [https://bugs.launchpad.net/tempest/+bug/1443445 #1443445] | * seemingly random tests fail due to ResonseNotReady exceptions in test setup (and sometimes teardown) as described in [https://bugs.launchpad.net/tempest/+bug/1443445 #1443445] | ||
Revision as of 08:55, 14 April 2015
| 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.
Other bugs that where found by Quobyte CI: |
