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
Validate awsendpoint deletion #1813
Validate awsendpoint deletion #1813
Conversation
PTAL @sjenning |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: enxebre 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 |
I have observed this in the past as well |
/test e2e-aws |
1 similar comment
/test e2e-aws |
/test e2e-aws |
2 similar comments
/test e2e-aws |
/test e2e-aws |
/retest-required |
/retest-required |
/test e2e-aws |
3 similar comments
/test e2e-aws |
/test e2e-aws |
/test e2e-aws |
/retest-required |
With current implementation the cpo private link controller will consider deletion successfull after making the request, however if the resource keeps existing somehow in AWS it would prevent the deletion of the awsendpointService resource by the HO AWSEndpointServiceReconciler with "failed to delete resource: Service has existing active VPC Endpoint connections!" https://issues.redhat.com/browse/HOSTEDCP-597
e16931c
to
54a48b6
Compare
✅ Deploy Preview for hypershift-docs ready!
To edit notification comments on pull requests, go to your Netlify site settings. |
/test e2e-aws |
3 similar comments
/test e2e-aws |
/test e2e-aws |
/test e2e-aws |
/test e2e-aws |
2 similar comments
/test e2e-aws |
/test e2e-aws |
@enxebre: The following tests failed, say
Full PR test history. Your PR dashboard. 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/test-infra repository. I understand the commands that are listed here. |
/test e2e-aws |
/lgtm |
What this PR does / why we need it:
With current implementation the cpo private link controller will consider deletion successfull after making the request, however if the resource keeps existing somehow in AWS it would prevent the deletion of the awsendpointService resource by the HO AWSEndpointServiceReconciler with "failed to delete resource: Service has existing active VPC Endpoint connections!"
Which issue(s) this PR fixes (optional, use
fixes #<issue_number>(, fixes #<issue_number>, ...)
format, where issue_number might be a GitHub issue, or a Jira story:Ref https://issues.redhat.com/browse/HOSTEDCP-597
Checklist