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

Automate e2e tests for leaked ENIs #690

Closed
jaypipes opened this issue Oct 29, 2019 · 2 comments
Closed

Automate e2e tests for leaked ENIs #690

jaypipes opened this issue Oct 29, 2019 · 2 comments
Assignees
Labels
priority/P2 Low priority, nice to have. testing

Comments

@jaypipes
Copy link
Contributor

jaypipes commented Oct 29, 2019

We currently run some manual e2e tests that attempt to emulate the situations where we know (#69, #608) ENIs may be leaked and catch these situations (#624, #645).

We need to automate the running of these e2e tests and gate all merges to prevent regressions.

@jaypipes jaypipes changed the title e2e tests for leaked ENIs Automate e2e tests for leaked ENIs Oct 29, 2019
@mogren mogren added the priority/P2 Low priority, nice to have. label Nov 4, 2019
@jayanthvn jayanthvn assigned cgchinmay and Shreya027 and unassigned abhipth Oct 19, 2021
@jayanthvn
Copy link
Contributor

This is added to the new integration framework -

- Manually force detach an ENI
- Let the cni cleanup routine start
- Verify that the ENI is cleaned up.

@github-actions
Copy link

⚠️COMMENT VISIBILITY WARNING⚠️

Comments on closed issues are hard for our team to see.
If you need more assistance, please open a new issue that references this one.
If you wish to keep having a conversation with other community members under this issue feel free to do so.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
priority/P2 Low priority, nice to have. testing
Projects
None yet
Development

No branches or pull requests

7 participants