GitLab endpoint test - Retry on connection refused

What does this MR do?

By default curl only retries transient errors. Sometimes the ingress controller is not yet ready to serve requests, resulting in Connection refused errors, which are not considered transient. This stops the retry mechanism.

By passing --retry-connrefused this can be avoided. https://everything.curl.dev/usingcurl/downloads/retry.html#connection-refused

A more aggresive form is --retry-all-errors: https://everything.curl.dev/usingcurl/downloads/retry.html#retry-on-any-and-all-errors

Checklist

See Definition of done.

For anything in this list which will not be completed, please provide a reason in the MR discussion.

Required

• Merge Request Title and Description are up to date, accurate, and descriptive
• MR targeting the appropriate branch
• MR has a green pipeline on GitLab.com
• When ready for review, MR is labeled "~workflow::ready for review" per the Distribution MR workflow

Expected (please provide an explanation if not completing)

• Test plan indicating conditions for success has been posted and passes
• Documentation created/updated
• Tests added
• Integration tests added to GitLab QA
• Equivalent MR/issue for omnibus-gitlab opened
• Validate potential values for new configuration settings. Formats such as integer 10, duration 10s, URI scheme://user:passwd@host:port may require quotation or other special handling when rendered in a template and written to a configuration file.

Related issues