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

Log RBD info and RBD status in E2E validateRBDImageCount function in case of failure #4547

Open
Madhu-1 opened this issue Apr 5, 2024 · 4 comments
Assignees
Labels
component/testing Additional test cases or CI work good first issue Good for newcomers

Comments

@Madhu-1
Copy link
Collaborator

Madhu-1 commented Apr 5, 2024

          > > /retest ci/centos/mini-e2e/k8s-1.29

spurious failure, the logs show that an image was not cleaned up (yet?):

[FAILED] backend images not matching kubernetes resource count,image count 1 kubernetes resource count 0

i think we need to update the validation function to print rbd info and rbd status of each images to get more clarity what happened. it looks like the image is opened by someone but not closed? not sure who

Originally posted by @Madhu-1 in #4499 (comment)

@nixpanic nixpanic added the component/testing Additional test cases or CI work label Apr 5, 2024
@Madhu-1 Madhu-1 added the good first issue Good for newcomers label May 7, 2024
@black-dragon74
Copy link
Member

print rbd info and rbd status of each images to get more clarity what happened.

Only in the case of failure, right?

@Madhu-1
Copy link
Collaborator Author

Madhu-1 commented Aug 27, 2024

yes thats correct

@OdedViner
Copy link
Contributor

/assign

Copy link

Thanks for taking this issue! Let us know if you have any questions!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
component/testing Additional test cases or CI work good first issue Good for newcomers
Projects
None yet
Development

No branches or pull requests

4 participants