You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have integrated an E2E testing flow which creates a cluster claim using this example and expect it to be ready after waiting enough.
This works fine with running the e2e target locally with:
export UPTEST_AWS_CREDS=$(cat ~/.aws/credentials)
make e2e
However, it fails with timeouts when we run it with GitHub Action CI. When I observe the resources, I am seeing that there are resources in Ready=True, Synced=False with the event observe failed: cannot run plan: plan failed. See the actions run for this PR for more details.
This is most probably due to limited compute resources with GitHub Actions runners and not a bug for platform-ref-aws but worths further investigation and we need a way to make this work for automated e2e testing.
What happened?
We have integrated an E2E testing flow which creates a cluster claim using this example and expect it to be ready after waiting enough.
This works fine with running the e2e target locally with:
However, it fails with timeouts when we run it with GitHub Action CI. When I observe the resources, I am seeing that there are resources in Ready=True, Synced=False with the event
observe failed: cannot run plan: plan failed
. See the actions run for this PR for more details.This is most probably due to limited compute resources with GitHub Actions runners and not a bug for
platform-ref-aws
but worths further investigation and we need a way to make this work for automated e2e testing.How can we reproduce it?
Open a PR and add a comment with
/test-e2e
What environment did it happen in?
GitHub Actions.
cluster-dump.zip
The text was updated successfully, but these errors were encountered: