gate-check logging improvements
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack-Ansible |
Fix Released
|
Medium
|
Tom Cameron | ||
Icehouse |
Fix Released
|
Medium
|
Jesse Pretorius | ||
Juno |
Fix Released
|
Medium
|
Ian Cordasco | ||
Trunk |
Fix Released
|
Medium
|
Tom Cameron |
Bug Description
Currently we only make use of the console output for all gate check debugging. The console log is very verbose and often doesn't have the real information we need in order to identify the problem properly.
I suggest that we do the following:
- collect other logs which can add insight and store them as artifacts
- split outputs into multiple logs so that the console outputs are closer to a summary... we should be able to use it almost like a dashboard to determine where else to look for details of what went wrong
- split the host information into separate logs, and if possible collect similar information from inside the containers
- run ansible in standard mode (not very verbose mode), but have it output debug logs to a file (not sure whether this is possible somehow)
Whatever is done needs to work for both openstack-infra and external CI's.
Some references:
- https:/
- https:/
description: | updated |
description: | updated |
Changed in openstack-ansible: | |
status: | New → Triaged |
assignee: | nobody → Tom Cameron (tom-cameron) |
Related fix proposed to branch: master /review. openstack. org/159931
Review: https:/