Rafael F.

> > Did you try such a scenario? > > I was not expecting such a solution to be accepted by capa devs. Let me try to run the openshift...

Update: rebased on top of master so I could rebase https://github.com/openshift/installer/pull/8927 and re-run the Openshift e2e tests.

@AndiDog I haven't seen a single regression in the OCP e2e tests so far. Anything else I can do to move this along?

``` STEP: Failed to create CloudFormation stack in attempt 8: failed to create CF stack: failed to wait for AWS CloudFormation stack to be CreateComplete: ResourceNotReady: failed waiting for successful...

I suspect the timeout failures in the e2e are due to https://github.com/kubernetes-sigs/cluster-api-provider-aws/issues/5131

Update: rebased on top of current main. /test pull-cluster-api-provider-aws-e2e /test pull-cluster-api-provider-aws-e2e-eks

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

/remove-lifecycle rotten Bug is still valid (see https://github.com/kubernetes-sigs/cluster-api-provider-aws/pull/5093#issuecomment-2403294134) and there is a proposed fix at https://github.com/kubernetes-sigs/cluster-api-provider-aws/pull/5093

Instead of the validation, we can also do https://github.com/kubernetes-sigs/cluster-api-provider-aws/pull/4892

/close