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. Try rechecking or asking on #tripleo +if there's an ongoing infra issue.
+ +Look for a line above the PLAY RECAP that starts with +"fatal:". If no such line is found, try searching for other PLAY RECAP +lines or other error outputs.
+ +If this "fatal" line contains the execution of a shell script and redirects +to a log, check which machine that task ran on. Look under that node's +directory in the logs to find the file.
+ +Example output:
+
+fatal: [undercloud]: FAILED! => {"changed": true, "cmd": "set -o pipefail &&
+/home/jenkins/overcloud-prep-images.sh 2>&1 | awk '{ print
+strftime(\"%Y-%m-%d %H:%M:%S |\"), $0; fflush(); }' >
+/home/stack/overcloud_prep_images.log", "failed": true, "rc": 1}
+
+PLAY RECAP *********************************************************************
+
In this case the overcloud-prep-images.sh script failed, which
+is redirected to /home/jenkins/overcloud_prep_images.log
+ on the undercloud.
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.
+ +