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
metrics: Improve latency network cleanup #8659
metrics: Improve latency network cleanup #8659
Conversation
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.
good job, just a couple of comments inline
kubectl delete -f latency-client.yaml | ||
} | ||
|
||
trap latency_cleanup EXIT |
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.
If the script ends before the server and clients pods are created, call to latency_cleanup
could report error.
I can think of two options, :
- You can make that the lines that deletes the pods return always true
- or move the
trap
line just after the creation of the server and client pods.
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.
thanks @dborquez for the feedback changes applied
ba89fbc
to
6350df9
Compare
This PR improves the latency network cleanup by removing the pods even if the test fails. Fixes kata-containers#8658 Signed-off-by: Gabriela Cervantes <gabriela.cervantes.tellez@intel.com>
6350df9
to
8151117
Compare
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.
thank you @GabyCT LGTM
This PR improves the latency network cleanup by removing the pods even if the test fails.
Fixes #8658