[DO NOT MERGE] Increase timeout to test e2e failures on OCPs

[razo7]

DO NOT MERGE for now

Why we need this PR

Changes made

Which issue(s) this PR fixes

Test plan

[openshift-ci]

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: razo7

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

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [razo7]

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

[razo7]

/test 4.16-openshift-e2e
/test 4.17-openshift-e2e

[razo7]

/test 4.16-openshift-e2e
/test 4.17-openshift-e2e

[openshift-ci]

@razo7: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
ci/prow/4.17-openshift-e2e	a4c446a	link	true	/test 4.17-openshift-e2e
ci/prow/4.16-openshift-e2e	a4c446a	link	true	/test 4.16-openshift-e2e

Full PR test history. Your PR dashboard.

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. I understand the commands that are listed here.

[razo7]

Tests fail regardless of extending the timeout, so I am closing the PR over #159 which will improve e2e.

When the AWS agent fails there is a context timed out, and the retryCount should be higher...

2024-11-06T13:05:00.58981258Z	INFO	executer	command failed	{"uid": "b288603c-a1a7-422c-a9f4-35f44a0f7924", "response": "", "errMessage": "2024-11-06 13:05:00,545 ERROR: Failed: Unable to obtain correct plug status or plug is not available\n\n\n", "err": "exit status 1"}
2024-11-06T13:05:21.362701084Z	INFO	executer	command failed	{"uid": "b288603c-a1a7-422c-a9f4-35f44a0f7924", "response": "", "errMessage": "2024-11-06 13:05:21,306 ERROR: Failed: Unable to obtain correct plug status or plug is not available\n\n\n", "err": "exit status 1"}
2024-11-06T13:05:42.159825008Z	INFO	executer	command failed	{"uid": "b288603c-a1a7-422c-a9f4-35f44a0f7924", "response": "", "errMessage": "2024-11-06 13:05:42,063 ERROR: Failed: Unable to obtain correct plug status or plug is not available\n\n\n", "err": "exit status 1"}
2024-11-06T13:06:02.950947281Z	INFO	executer	command failed	{"uid": "b288603c-a1a7-422c-a9f4-35f44a0f7924", "response": "", "errMessage": "2024-11-06 13:06:02,905 ERROR: Failed: Unable to obtain correct plug status or plug is not available\n\n\n", "err": "exit status 1"}
2024-11-06T13:06:23.761307092Z	INFO	executer	command failed	{"uid": "b288603c-a1a7-422c-a9f4-35f44a0f7924", "response": "", "errMessage": "2024-11-06 13:06:23,673 ERROR: Failed: Unable to obtain correct plug status or plug is not available\n\n\n", "err": "exit status 1"}
2024-11-06T13:06:23.761355516Z	INFO	executer	fence agent done	{"uid": "b288603c-a1a7-422c-a9f4-35f44a0f7924", "fence_agent": "fence_aws", "stdout": "", "stderr": "2024-11-06 13:06:23,673 ERROR: Failed: Unable to obtain correct plug status or plug is not available\n\n\n", "err": "exit status 1"}
2024-11-06T13:06:23.761377757Z	INFO	executer	fence agent context timed out