-
Notifications
You must be signed in to change notification settings - Fork 578
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
✨ feat: Remove owned VPCEs when deleting VPC. #5193
Conversation
Welcome @s3rj1k! |
Hi @s3rj1k. Thanks for your PR. I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. 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. |
/ok-to-test |
379006c
to
b23c56c
Compare
Tests are green 🎉 |
/test ? |
@richardcase: The following commands are available to trigger required jobs:
The following commands are available to trigger optional jobs:
Use
In response to this:
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. |
/test pull-cluster-api-provider-aws-e2e |
65e62c7
to
b23c56c
Compare
969db9a
to
55c089c
Compare
55c089c
to
b43ee71
Compare
d34da13
to
6eb0e44
Compare
6eb0e44
to
0c80965
Compare
/test pull-cluster-api-provider-aws-e2e-eks |
A flake with the cloudformation creation, so: /test pull-cluster-api-provider-aws-e2e |
due to "The security token included in the request is invalid." /test pull-cluster-api-provider-aws-e2e |
due to "Should've eventually succeeded creating an AWS CloudFormation stack" |
due to "The security token included in the request is invalid." /test pull-cluster-api-provider-aws-e2e-eks |
due to "Timed out after 2700.003s. Should've eventually succeeded creating an AWS CloudFormation stack" /test pull-cluster-api-provider-aws-e2e-eks |
I've seen intermittent issue with the CF stack before, but looks like it's happening more often now. I think perhaps we need to log the AWS account where the failures are occurring, it could be with specific AWS accounts that boskos is handing to us. I will have a look in the morning. Thanks for persevering @s3rj1k . |
One out of 1 tests failed with "Timed out after 1800.000s. /test pull-cluster-api-provider-aws-e2e-eks |
@s3rj1k - they passed :) |
From my side: /approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: richardcase 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:
Approvers can indicate their approval by writing |
For lgtm: /assign @AndiDog |
@richardcase Brute-forced e2e into passing :) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice fix.
/lgtm
/kind feature
Fixes #5192
Special notes for your reviewer:
Checklist: