Bug 1599829 - [RFE] Creation of an out-of-band framework that would trigger sanity check of a environment before upgrade/update/ffwd
Summary: [RFE] Creation of an out-of-band framework that would trigger sanity check of...
Keywords:
Status: ASSIGNED
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: RFEs
Version: unspecified
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: RHOS Maint
QA Contact:
URL: https://blueprints.launchpad.net/trip...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-07-10 16:53 UTC by Sofer Athlan-Guyot
Modified: 2018-09-03 11:19 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:


Attachments (Terms of Use)

Description Sofer Athlan-Guyot 2018-07-10 16:53:38 UTC
Description of problem:

The long running environment we encounter during upgrade/update/ffwd may have specific issues that are rarely encountered during testing due the the sort running time and few data those test environment have.

So we need to have a pre-flight check done.

This should be done outside of director framework (no heat/mistral ...) as we want to check both undercloud and overcloud.

This shouldn't be done during the upgrade so that it doesn't take unnecessary time in the maintenance window the operator will have for the upgrade/update/ffwd.

It should be very easy to read so that anybody can contribute.  

It should be very easy to extend so that operator could add their own test in whatever language they see fit (shell/python/...whatever)

It could trigger purge jobs on the costumer environment provided the purge job exists and the operator agree.

It should output human readable report or json like output for further processing.

Comment 1 Sofer Athlan-Guyot 2018-07-10 17:10:04 UTC
It should be able to run specific tests based on currently installed OSP
version.

Comment 2 Sofer Athlan-Guyot 2018-07-10 17:13:40 UTC
Some examples of the common issue are:
 - db purge not working;
 - .ini/.json not updated because of costumer modification;
 - missing package;
 - undeleted packages;

Comment 3 Cédric Jeanneret 2018-07-18 12:03:16 UTC
We heard you :).

Please jump in the spec redaction and add your needs, thoughts and so on. We're going to make a cool thing together.


Note You need to log in before you can comment on or make changes to this bug.