Closed akrzos closed 6 years ago
I suggest we use block/rescue/always statements around failure points to allow collection of valuable remote logs automaticlly
For instance this spot: https://github.com/redhat-performance/tripleo-quickstart-scalelab/blob/master/roles/overcloud-deploy/tasks/main.yml#L26-L27
We could do something like the block statement in this playbook: https://github.com/akrzos/deploy-microcloud/blob/06231d0a3edfc893233bd97a4e376a3af41b0155/roles/016-overcloud-deploy/tasks/main.yml#L7
Artifact directory has been added and overcloud deploy artifact is collected. In flight PR for undercloud install and other artifacts.
I suggest we use block/rescue/always statements around failure points to allow collection of valuable remote logs automaticlly
For instance this spot: https://github.com/redhat-performance/tripleo-quickstart-scalelab/blob/master/roles/overcloud-deploy/tasks/main.yml#L26-L27
We could do something like the block statement in this playbook: https://github.com/akrzos/deploy-microcloud/blob/06231d0a3edfc893233bd97a4e376a3af41b0155/roles/016-overcloud-deploy/tasks/main.yml#L7