🤖 Triggering CI on branch 'release-next' after synching to upstream/main

[alanfx]

No description provided.

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: alanfx

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 [alanfx]

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

[aliok]

/retest

[matzew]

/test 48-e2e-aws-ocp-48

[matzew]

/test 48-e2e-aws-ocp-48

[aliok]

/test 48-e2e-aws-ocp-48

failed to apply Terraform

[matzew]

/test 48-e2e-aws-ocp-48

[openshift-ci]

@alanfx: The following tests failed, say /retest to rerun all failed tests:

Test name	Commit	Details	Rerun command
ci/prow/47-e2e-aws-ocp-47	f325995	link	/test 47-e2e-aws-ocp-47
ci/prow/48-e2e-aws-ocp-48	f325995	link	/test 48-e2e-aws-ocp-48

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

[matzew]

merged.... to see if there is some image cache issue.

will respin later....