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

(SUP-2952) (Issue #193) - Retry if provisioning target returns a 500 #194

Merged
merged 4 commits into from
May 6, 2022

Conversation

BartoszBlizniak
Copy link
Contributor

Prior to this commit, there was no option to retry the provisioning of an environment which caused the entire workflow to fail, this commit ensures that we try to provision the environment up to 5 times before failing.

@chelnak
Copy link
Contributor

chelnak commented Apr 22, 2022

re-try logic with default parameter
@MartyEwings
Copy link

@BartoszBlizniak if you change the fixtures in one of our test branches in a low priority module, to point to your fork and give it a shot? we should be able to test this

BartoszBlizniak and others added 2 commits May 6, 2022 13:52
Fixing string error

fixing string conversion error

fixing string conversion error

fixing string conversion error
@BartoszBlizniak
Copy link
Contributor Author

Hey regarding testing,

I have a question, how fast does the max_retries execute because this might just take a second to re-try so we won’t be able to spot that in the actual runs.

The only run that was off by around 30seconds that I managed to get is this one:

run of 1m38s

https://github.com/puppetlabs/puppetlabs-pe_status_check/runs/6324457998?check_suite_focus=true

compared to average 55 seconds:

https://github.com/puppetlabs/puppetlabs-pe_status_check/runs/6324451685?check_suite_focus=true

In both Ubuntu might be off by around 30s too

That said, I've ran around 15 tests and all provisioned successfully so we can assume that the code didn't break any provisioning here.

@david22swan david22swan merged commit 4beb5aa into puppetlabs:main May 6, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

6 participants