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
  • screen-c-api.txt.gz: cinder-api
  • screen-c-bak.txt.gz: cinder-backup
  • screen-c-sch.txt.gz: cinder-scheduler
  • screen-c-vol.txt.gz: cinder-volume
• ceilometer
  • screen-ceilometer-acentral.txt.gz: ceilometer-agent-central
  • screen-ceilometer-acompute.txt.gz: ceilometer-agent-compute
  • screen-ceilometer-alarm-evaluator.txt.gz: ceilometer-alarm-evaluator
  • screen-ceilometer-alarm-notifier.txt.gz: ceilometer-alarm-notifier
  • screen-ceilometer-anotification.txt.gz: ceilometer-agent-notifier
  • screen-ceilometer-api.txt.gz: ceilometer-api
  • screen-ceilometer-collector.txt.gz: ceilometer-collector
• glance
  • screen-g-api.txt.gz: glance-api
  • screen-g-reg.txt.gz: glance-registry
• heat
  • screen-h-api-cfn.txt.gz: heat-api-cfn
  • screen-h-api-cw.txt.gz: heat-api-cloudwatch
  • screen-h-api.txt.gz: heat-api
  • screen-h-eng.txt.gz: heat-engine
• horizon
  • horizon_error.txt.gz: horizon logs
• ironic
  • ironic-bm-logs/: output from the last successful boot of an ironic "bare metal" VM
  • screen-ir-api.txt.gz: ironic-api
  • screen-ir-cond.txt.gz: ironic-conductor
• keystone
  • keystone.txt.gz: keystone log (Apache Httpd)
  • keystone_access.txt.gz: keystone access log (Apache Httpd)
  • screen-key.txt.gz: keystone log (eventlet)
• nova
  • screen-n-api.txt.gz: nova-api
  • screen-n-cond.txt.gz: nova-conductor
  • screen-n-cpu.txt.gz: nova-compute
  • screen-n-crt.txt.gz: nova-cert
  • screen-n-net.txt.gz: nova-network
  • screen-n-obj.txt.gz: nova-objectstore
  • screen-n-sch.txt.gz: nova-scheduler
• neutron
  • screen-q-agt.txt.gz: neutron-openvswitch-agent
  • screen-q-dhcp.txt.gz: neutron-dhcp-agent
  • screen-q-lbaas.txt.gz: neutron-lbaas-agent
  • screen-q-meta.txt.gz: neutron-metadata-agent
  • screen-q-metering.txt.gz: neutron-metering-agent
  • screen-q-svc.txt.gz: neutron-server
  • screen-q-vpn.txt.gz: neutron-vpn-agent
• swift
  • screen-s-account.txt.gz: swift-account-server
  • screen-s-container.txt.gz: swift-container-server
  • screen-s-object.txt.gz: swift-object-server
  • screen-s-proxt.txt.gz: swift-proxy-server
• system
  • pip-freeze.txt.gz: List of pip installed python packages. Output of 'pip freeze'
  • dpkg-l.txt.gz: List of apt-get installed packages. Output of 'dpkg -l'
  • df.txt.gz:
  • syslog.txt.gz: syslog for the test slave
  • screen-dstat.txt.gz: dstat output during the test job
  • sudoers.txt.gz: sudoers file
• trove
  • screen-tr-api.txt.gz: trove-api
  • screen-tr-cond.txt.gz: trove-conductor
  • screen-tr-tmgr.txt.gz: trove-taskmanager
• tempest
  • tempest.txt.gz: Tempest log file
  • tempest_conf.txt.gz: Tempest config file
  • subunit_log.txt.gz: Subunit v1 stream from tempest run
  • testr_results.html.gz: html formatted output of test results
• devstack
  • devstacklog.txt.gz: Devstack log

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.

About this Help

This help file is part of the openstack-infra/system-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.