Guide to Devstack Gate Logs

Above is a collection of log files from the current tempest run. Within them should be everything you need to get to the bottom of a test failure. The screen-* logs will be your most valuable tools in this process. Use the timestamp of a the failed test in the current tempest run.

Nova Compute Fails

If there is a compute test failure, especially a server not getting created correctly, or being in an unexpected state, the following is typically the most fruitful order to look at things:

• screen-n-api.txt.gz - the nova api log, which will show top level failures. Make sure the request that was being sent in actually suceeded.
• screen-n-cpu.txt.gz - the nova compute log. If a libvirt or qemu issue happened during guest creation it will be here.
• screen-n-sch.txt.gz - the nova scheduler. Some times there are races in allocating resources, and the scheduler will throw a WARNING if it couldn't allocate the requested resources.
• all other nova logs

Cinder Volume Fails

If there is a volume failure in the test, the following is typically the most fruitful order to look at things:

• screen-c-api.txt.gz - the cinder api log, which will show top level failures. Make sure the request that was being sent in actually suceeded.
• screen-c-vol.txt.gz - the cinder agent log. If there was a local allocation error it will be here.
• screen-c-sch.txt.gz - the cinder scheduler. Some times there are races in allocating resources, and the scheduler will throw a WARNING if it couldn't allocate the requested resources.

About this Help

This help file is part of the openstack-infra/config project, and can be found at modules/openstack_project/files/logs/help/tempest_logs.html . The file can be updated via the standard OpenStack Gerrit Review process.