[QA] Destructive tests against network partitions TBD

Bug #1581437 reported by Bogdan Dobrelya
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Fuel for OpenStack
Confirmed
High
Fuel QA Team

Bug Description

Fuel integration testing lacks one important sub-type of destructive testing to provide recovery/self-heal coverage for clusters, which is to check network partitions tolerance and post-recovery behavior.

The idea is to run integration tests of that type either against a several components, like Corosync/Pacemaker/DB/MQ, or a whole deployment done. And with leveraging either existing frameworks like Jepsen's Nemesis or written ground up in Fuel QA codebase as well.

I provided example approach with Jepsen [0]. Details may be read there as well.
This work allowed me to discover ~10 high bugs related to DB cluster deployments and several bugs to MQ. You can find the list of DB bugs in this backport patch (just gives a nice view) [1].

[0] https://goo.gl/VHyIIE
[1] https://review.openstack.org/#/c/315989/

Tags: area-qa
Changed in fuel:
importance: Undecided → High
milestone: none → 10.0
assignee: nobody → Fuel QA Team (fuel-qa)
tags: added: area-qa
description: updated
Maciej Relewicz (rlu)
Changed in fuel:
status: New → Confirmed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.