Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow playbook to run if SCM access is restored during retries. #13

Open
dmetzger57 opened this issue Jun 22, 2020 · 0 comments
Open

Allow playbook to run if SCM access is restored during retries. #13

dmetzger57 opened this issue Jun 22, 2020 · 0 comments

Comments

@dmetzger57
Copy link

dmetzger57 commented Jun 22, 2020

Original BZ: https://bugzilla.redhat.com/show_bug.cgi?id=1835226

Description of problem:
When using a playbook as part of an automate provision, if ansible-runner is used to run a playbook and the initial connection to the SCM fails, retries of the task will never succeed, even if connectivity is resumed before all attempts are made.
How reproducible:
all the time

Steps to Reproduce:

  1. set up an automate that calls a playbook as part of provisioning (using ansible-runner and a SCM)
  2. break connectivity to the SCM
  3. initiate a provisioning
  4. restore connectivity before all retries are exhausted

Actual results:
failure to connect will cause the task to fail, then be retried.

Expected results:
when connectivity is restored, attempts should not fail anymore.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants