🌱 test: e2e: make managed suite more robust to errors with Eventually()

[damdo]

What type of PR is this?
/kind flake

What this PR does / why we need it:
make managed suite more robust to errors with Eventually()

Special notes for your reviewer:
Trying to address issues like the ones seen here: https://prow.k8s.io/view/gs/kubernetes-ci-logs/pr-logs/pull/kubernetes-sigs_cluster-api-provider-aws/5211/pull-cluster-api-provider-aws-e2e-eks/1856371404925046784

NONE

[damdo]

/assign @richardcase @nrb

[damdo]

/test ?

[k8s-ci-robot]

@damdo: The following commands are available to trigger required jobs:

• /test pull-cluster-api-provider-aws-build
• /test pull-cluster-api-provider-aws-build-docker
• /test pull-cluster-api-provider-aws-test
• /test pull-cluster-api-provider-aws-verify

The following commands are available to trigger optional jobs:

• /test pull-cluster-api-provider-aws-apidiff-main
• /test pull-cluster-api-provider-aws-e2e
• /test pull-cluster-api-provider-aws-e2e-blocking
• /test pull-cluster-api-provider-aws-e2e-clusterclass
• /test pull-cluster-api-provider-aws-e2e-conformance
• /test pull-cluster-api-provider-aws-e2e-conformance-with-ci-artifacts
• /test pull-cluster-api-provider-aws-e2e-eks
• /test pull-cluster-api-provider-aws-e2e-eks-gc
• /test pull-cluster-api-provider-aws-e2e-eks-testing

Use /test all to run the following jobs that were automatically triggered:

• pull-cluster-api-provider-aws-apidiff-main
• pull-cluster-api-provider-aws-build
• pull-cluster-api-provider-aws-build-docker
• pull-cluster-api-provider-aws-test
• pull-cluster-api-provider-aws-verify

In response to this:

/test ?

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.

[damdo]

/test pull-cluster-api-provider-aws-e2e-eks

[damdo]

Failed is unrelated (due to AWS CloudFormation stack)

/test pull-cluster-api-provider-aws-e2e-eks

[k8s-ci-robot]

[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 ask for approval from nrb. For more information see the Kubernetes Code Review Process.

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

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

[damdo]

/test pull-cluster-api-provider-aws-e2e-eks

[damdo]

/test pull-cluster-api-provider-aws-e2e-eks

[damdo]

/test pull-cluster-api-provider-aws-e2e-eks

[damdo]

/test pull-cluster-api-provider-aws-test

[damdo]

/test pull-cluster-api-provider-aws-e2e-eks

[damdo]

/test pull-cluster-api-provider-aws-e2e-eks

[damdo]

/test pull-cluster-api-provider-aws-e2e-eks

[damdo]

/test pull-cluster-api-provider-aws-e2e-eks

[damdo]

/test pull-cluster-api-provider-aws-e2e-eks

[damdo]

AWS Cloud formation stack timed out

/test pull-cluster-api-provider-aws-e2e-eks

[damdo]

/test pull-cluster-api-provider-aws-e2e-eks

[k8s-ci-robot]

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

Test name	Commit	Details	Required	Rerun command
pull-cluster-api-provider-aws-e2e-eks	c0c1125	link	false	/test pull-cluster-api-provider-aws-e2e-eks

Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

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.

[damdo]

@richardcase do you have any idea on why waiting for addons fails so often?