diff options
| author | Radosław Piliszek <radoslaw.piliszek@gmail.com> | 2022-05-27 20:14:26 +0200 |
|---|---|---|
| committer | Radosław Piliszek <radoslaw.piliszek@gmail.com> | 2022-05-27 20:14:26 +0200 |
| commit | 153956e458157e44d73efc3dd369699ff20e4d12 (patch) | |
| tree | f8252e712869d76e47c2e9dc7ecbaa9663d42258 /zuul.d | |
| parent | 15a81a288369a770af6f6b3d88a47b39b4ce8c16 (diff) | |
| download | kolla-ansible-153956e458157e44d73efc3dd369699ff20e4d12.tar.gz kolla-ansible-153956e458157e44d73efc3dd369699ff20e4d12.zip | |
[CI] Nullify attempts
Per Clark Boylan's feedback [1], retries cause a retry not only
for pre playbook failures but also for cases where Ansible detects
network connectivity issues and they are caused by disks getting
filled to their fullest. This is an issue we experience that
sometimes results in a POST_FAILURE but certain FAILUREs are
retried which wastes CI resources.
The problematic jobs are ceph jobs. They are to be looked into.
Backport to all branches.
We can adjust retries for the core jobs that do not exhibit the
nasty behaviour but first we can try running without retries
to measure the troublesomeness.
[1] https://review.opendev.org/c/openstack/kolla-ansible/+/843536
Change-Id: I32fc296083b4881e8f457f4235a32f94ed819d9f
Diffstat (limited to 'zuul.d')
| -rw-r--r-- | zuul.d/base.yaml | 1 |
1 files changed, 0 insertions, 1 deletions
diff --git a/zuul.d/base.yaml b/zuul.d/base.yaml index 76e2b87bf..bd6c72c22 100644 --- a/zuul.d/base.yaml +++ b/zuul.d/base.yaml @@ -4,7 +4,6 @@ pre-run: tests/pre.yml run: tests/run.yml post-run: tests/post.yml - attempts: 5 timeout: 7200 post-timeout: 1800 required-projects: |