Please refer to the recreation instructions
Name | Last modified | Size | |
---|---|---|---|
Parent Directory | - | ||
quickstart_install.log | 2020-03-28 05:20 | 58K | |
zuul_console.json | 2020-03-28 05:20 | 1.1M | |
dns_cache.txt | 2020-03-28 05:20 | 18K | |
undercloud/ | 2020-03-28 05:23 | - | |
_No_failure_reason_found.log | 2020-03-28 05:23 | 40 | |
ara.json | 2020-03-28 05:23 | 0 | |
ara.oooq.uc.json | 2020-03-28 05:23 | 0 | |
ara.oooq.oc.json | 2020-03-28 05:23 | 0 | |
reproducer-quickstart-deprecated/ | 2020-03-28 05:23 | - | |
reproducer-quickstart/ | 2020-03-28 05:23 | - | |
full_logs.html | 2020-03-28 05:23 | 530 | |
quickstart_collect_logs.log | 2020-03-28 05:23 | 1.9M | |
testrepository.subunit.gz | 2020-03-28 05:23 | 396 | |
quickstart_files/ | 2020-04-29 06:33 | - | |
Please refer to the recreation instructions
Note: These logs are only available in jobs that use OVB.
Check the base directory for a file called *failure_reason* for automatic failure detection. If no known error has been found the file will be named "No_failure_reason_found".
Most of the undercloud and overcloud deployment log files can be found in undercloud/home/zuul tracebacks and other errors are collected in the following log per node:
Next check the console log and search for PLAY RECAP. There are sometimes
multiple ansible runs in a job, usually the last one is the relevant.
If no PLAY RECAP text is found that usually means an infra failure
before Quickstart could even start.
If this is a different Ansible error, that could mean either an infra
problem (often has UNREACHABLE in the line) or a bug in Quickstart.
Ask on #tripleo to get help or open a bug on Launchpad. Add the "ci" tag if it's a CI issue and "quickstart" if you suspect that the bug is in Quickstart itself.
Finally try rechecking or asking on #tripleoThe logs contain files showing variables used in the job run.
Upstream OpenStack Health, Elastic Search and Kibana
Tools that will help you spot a trend in TripleO CI
Tools to compare one job to another.
As a debugging step, a job can be run manually with '-dryrun' appended to the job name. When the "playbook dry run" option is invoked, the playbooks will not execute and collect logs will not run but certain log files, including 'toci_env_args_output.log', which contains the environment variables used in the job, and playbook_executions.log will still be produced in the logs directory for inspection. This option serves to assist with debugging and to test the testing scripts themselves.