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

[BUG] retry state option unavailble when parallel is True #61630

Closed
6 tasks
garethgreenaway opened this issue Feb 11, 2022 · 0 comments · Fixed by #61631
Closed
6 tasks

[BUG] retry state option unavailble when parallel is True #61630

garethgreenaway opened this issue Feb 11, 2022 · 0 comments · Fixed by #61631
Assignees
Labels
Bug broken, incorrect, or confusing behavior severity-high 2nd top severity, seen by most users, causes major problems

Comments

@garethgreenaway
Copy link
Contributor

Description
When the retry options are set in a state and parallel is set to True, the job is rerun regardless of the original state results and the subsequent runs are not done in parallel.

Setup
Basic state that includes parallel: True and retry options:

{% set parallel = True %}
{% for i in range(1,5) %}
run {{ i }}:
  cmd.run:
    - name: /tmp/cmd.sh
    - parallel: {{ parallel }}
    - retry:
        attempts: 2
        until: True
        interval: 5
{% endfor %}
randomNumber=$(( $RANDOM % 2 ))

if [[ $randomNumber == 1 ]]; then
    echo "False"
    exit 1
else
    echo "True"
    exit 0
fi

Please be as specific as possible and give set-up details.

  • on-prem machine
  • VM (Virtualbox, KVM, etc. please specify)
  • VM running on a cloud service, please be explicit and add details
  • container (Kubernetes, Docker, containerd, etc. please specify)
  • or a combination, please be explicit
  • jails if it is FreeBSD
PASTE HERE

Additional context
Add any other context about the problem here.

@garethgreenaway garethgreenaway added Bug broken, incorrect, or confusing behavior needs-triage labels Feb 11, 2022
@garethgreenaway garethgreenaway self-assigned this Feb 11, 2022
@garethgreenaway garethgreenaway added Phosphorus v3005.0 Release code name and version and removed needs-triage labels Feb 11, 2022
@garethgreenaway garethgreenaway added this to the Phosphorus v3005.0 milestone Feb 11, 2022
@garethgreenaway garethgreenaway removed the Phosphorus v3005.0 Release code name and version label Feb 23, 2022
@OrangeDog OrangeDog added the severity-high 2nd top severity, seen by most users, causes major problems label Mar 14, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug broken, incorrect, or confusing behavior severity-high 2nd top severity, seen by most users, causes major problems
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants