NO-JIRA: Bump metal3-dev-env to e5cb63c

[mabulgu]

Bump metal3-dev-env pinned commit to e5cb63c6a9dcd0d4544a1ae6855c6769957a8984 which includes metal3-io/metal3-dev-env#1666.

This increases the DNF retry count from 3 to 5 and delay from 10s to 30s for all package installation Ansible tasks in metal3-dev-env. The "Refresh DNF cache" task was the weakest link with only 30s max wait (3 retries x 10s), which proved insufficient during extended EPEL mirror outages, causing recurring CI install failures.

The new values (5 retries x 30s = 150s max wait) are closer to what dev-scripts' own 01_install_requirements.sh already uses (MAX_RETRIES=5 with exponential backoff, up to 225s).

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign mkowalski for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[openshift-ci]

Hi @mabulgu. Thanks for your PR.

I'm waiting for a openshift-metal3 member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work.

Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[elfosardo]

/ok-to-test