Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

E2E test fails with Synced=False resources with 'plan failed' errors in CI #84

Closed
turkenh opened this issue Oct 21, 2022 · 1 comment
Closed
Labels
bug Something isn't working

Comments

@turkenh
Copy link
Member

turkenh commented Oct 21, 2022

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:

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.

Screen Shot 2022-10-21 at 14 26 34

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

@turkenh turkenh added the bug Something isn't working label Oct 21, 2022
@turkenh turkenh mentioned this issue Nov 10, 2022
1 task
@turkenh
Copy link
Member Author

turkenh commented Nov 22, 2022

I have validated this issue is no longer happening with the latest Provider AWS version, which includes this PR.

@turkenh turkenh closed this as completed Nov 22, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant