| 2015-02-25 11:39:11 |
Jesse Pretorius |
bug |
|
|
added bug |
| 2015-02-25 11:41:53 |
Jesse Pretorius |
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
Whatever is done needs to work for both openstack-infra and external CI's.
Some references:
- https://github.com/openstack-infra/project-config/blob/610bd506c457ab858971061c1718eae7f13ff8d6/jenkins/jobs/keystoneclient-functional.yaml#L32-L35
- https://github.com/openstack-infra/project-config/blob/610bd506c457ab858971061c1718eae7f13ff8d6/jenkins/jobs/macros.yaml#L522-L542 |
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, 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://github.com/openstack-infra/project-config/blob/610bd506c457ab858971061c1718eae7f13ff8d6/jenkins/jobs/keystoneclient-functional.yaml#L32-L35
- https://github.com/openstack-infra/project-config/blob/610bd506c457ab858971061c1718eae7f13ff8d6/jenkins/jobs/macros.yaml#L522-L542 |
|
| 2015-02-25 11:42:10 |
Jesse Pretorius |
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, 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://github.com/openstack-infra/project-config/blob/610bd506c457ab858971061c1718eae7f13ff8d6/jenkins/jobs/keystoneclient-functional.yaml#L32-L35
- https://github.com/openstack-infra/project-config/blob/610bd506c457ab858971061c1718eae7f13ff8d6/jenkins/jobs/macros.yaml#L522-L542 |
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://github.com/openstack-infra/project-config/blob/610bd506c457ab858971061c1718eae7f13ff8d6/jenkins/jobs/keystoneclient-functional.yaml#L32-L35
- https://github.com/openstack-infra/project-config/blob/610bd506c457ab858971061c1718eae7f13ff8d6/jenkins/jobs/macros.yaml#L522-L542 |
|
| 2015-02-25 20:15:53 |
Ian Cordasco |
openstack-ansible: status |
New |
Triaged |
|
| 2015-02-25 20:16:09 |
Ian Cordasco |
openstack-ansible: assignee |
|
Tom Cameron (tom-cameron) |
|
| 2015-03-05 10:10:06 |
Jesse Pretorius |
nominated for series |
|
openstack-ansible/icehouse |
|
| 2015-03-05 10:10:06 |
Jesse Pretorius |
bug task added |
|
openstack-ansible/icehouse |
|
| 2015-03-05 10:10:06 |
Jesse Pretorius |
nominated for series |
|
openstack-ansible/juno |
|
| 2015-03-05 10:10:06 |
Jesse Pretorius |
bug task added |
|
openstack-ansible/juno |
|
| 2015-03-05 10:10:06 |
Jesse Pretorius |
nominated for series |
|
openstack-ansible/trunk |
|
| 2015-03-05 10:10:06 |
Jesse Pretorius |
bug task added |
|
openstack-ansible/trunk |
|
| 2015-03-05 10:10:14 |
Jesse Pretorius |
openstack-ansible/trunk: status |
Triaged |
In Progress |
|
| 2015-03-05 10:10:18 |
Jesse Pretorius |
openstack-ansible/juno: status |
New |
In Progress |
|
| 2015-03-05 10:10:21 |
Jesse Pretorius |
openstack-ansible/icehouse: status |
New |
In Progress |
|
| 2015-03-05 10:10:23 |
Jesse Pretorius |
openstack-ansible/juno: importance |
Undecided |
Medium |
|
| 2015-03-05 10:10:25 |
Jesse Pretorius |
openstack-ansible/icehouse: importance |
Undecided |
Medium |
|
| 2015-03-05 10:11:30 |
Jesse Pretorius |
openstack-ansible/juno: assignee |
|
Ian Cordasco (icordasc) |
|
| 2015-03-05 10:11:34 |
Jesse Pretorius |
openstack-ansible/icehouse: assignee |
|
Jesse Pretorius (jesse-pretorius) |
|
| 2015-03-05 10:11:43 |
Jesse Pretorius |
openstack-ansible/juno: milestone |
|
10.1.3 |
|
| 2015-03-05 10:11:45 |
Jesse Pretorius |
openstack-ansible/icehouse: milestone |
|
9.0.7 |
|
| 2015-03-23 10:45:34 |
Jesse Pretorius |
openstack-ansible/icehouse: status |
In Progress |
Fix Committed |
|
| 2015-03-23 10:45:36 |
Jesse Pretorius |
openstack-ansible/juno: status |
In Progress |
Fix Committed |
|
| 2015-03-23 10:45:39 |
Jesse Pretorius |
openstack-ansible/trunk: status |
In Progress |
Fix Committed |
|
| 2015-04-01 16:24:07 |
Kevin Carter |
openstack-ansible/icehouse: status |
Fix Committed |
Fix Released |
|
| 2015-04-11 00:44:42 |
Kevin Carter |
openstack-ansible/juno: status |
Fix Committed |
Fix Released |
|
| 2015-05-08 20:18:46 |
Kevin Carter |
openstack-ansible/trunk: status |
Fix Committed |
Fix Released |
|
