Guide to Tempest Results Runs

You are looking at the full test results of a devstack setup and
tempest run for the OpenStack gate, as well as all the logs of all the
relevant services that were running during that tempest test run. From
them you should have enough information to debug.

How To Debug - Quickstart

scroll to the end of console.html

work your way backwards until the first failing test

copy the timestamp of that failing test

go into logs directory and look at that time stamp in related
service logs for traces, failures, or other oddities

File Overview

console.html

This file contains the stdout/stderr console of the devstack-gate
job. The basic flow of the file goes as follows:

Boot guest from base Linux image

Use devstack to install all required packages (debs and pips)

Use devstack to setup all the services from upstream master except
for the particular project being tested, which is pulled from
gerrit.

Run devstack exercises (very basic sanity checking)

Run tempest tests

All the devstack setup is done under bash tracing, so
is extremely verbose. This is to ensure enough data is captured
so that you can debug failures in the gate with the information provided.

The tempest tests are the last 1% of the console.html. When looking
at failures it is typical best to start at the end of the file and
work backwards.

logs

The logs directory contains all the screen logs
from all the services during the devstack-gate run.