You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
set up an automate that calls a playbook as part of provisioning (using ansible-runner and a SCM)
break connectivity to the SCM
initiate a provisioning
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.
The text was updated successfully, but these errors were encountered:
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:
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.
The text was updated successfully, but these errors were encountered: