-
Notifications
You must be signed in to change notification settings - Fork 6
Don't uninstall sr tools on failed teardown #357
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
base: master
Are you sure you want to change the base?
Conversation
3287421
to
b10d6d5
Compare
A PR title is important. It's our first contact with the change. Here, it looks like the title currently says the contrary of what the PR actually does :) |
Indeed, it does, I made a typo writing it ^^' That's fixed I'll add a proper description once I'm done with the content of the PR, it's not ready yet :) |
b10d6d5
to
46cd8ab
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.
LGTM
I had the same problem with xfsprogs
yesterday. Could you also do that for the XFS SRs ?
Leave glusterfs tools in place for manual cleanup after a failed SR cleanup Signed-off-by: Antoine Bartuccio <[email protected]>
Leave linstor tools in place for manual cleanup after a failed SR cleanup Signed-off-by: Antoine Bartuccio <[email protected]>
Leave xfs tools in place for manual cleanup after a failed SR cleanup Signed-off-by: Antoine Bartuccio <[email protected]>
51d6dd5
to
db8d29c
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.
LGTM.
For the next PR, you should separate the type annotations and the actual code changes in multiple commits, to ease the review.
When SR cleanup fails on linstor and glusterfs tests, a manual cleanup is needed.
Since tests removes software tools needed to interact with those technologies, we have to install them again to cleanup and it's annoying.
This PR ensures that those tools are still installed on the host machine when this scenario happens