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 the failed test in
the current tempest run.
Types of logs
- cinder
- ceilometer
- designate
- glance
- heat
- horizon
- ironic
- keystone
- nova
- neutron
- swift
- system
- trove
- tempest
- devstack
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 succeeded.
- 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 succeeded.
- 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.
Designate Zone Fails
If a DNS Zone fails to reach the DNS Server, the following is
typically the most fruitful order to look at things:
- screen-designate-pool-manager.txt.gz - the
pool manager logs will show if there was an error creating the zone on the
server, or if it had issues loading the driver for the DNS Server
- screen-designate-mdns.txt.gz - the
mini dns server will log if it received a AFXR request, or if the DNS Server has too low a
serial number. This shows either a communications problem or a server configuration issue.
- screen-designate-central.txt.gz - designate
central will most likely contain the error it it is not in pool manager or mini dns.
All of the DB access runs though here, and all of the validation logic is also here.
About this Help
This help file is part of the
openstack/devstack-gate
project, and can be found at
help/tempest-logs.html
.
The file can be updated via the standard OpenStack Gerrit Review process.