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
qa: make teardown behavior consistent for kclient/fuse mounts #56669
Conversation
Signed-off-by: Patrick Donnelly <pdonnell@redhat.com>
jenkins test make check arm64 |
1 similar comment
jenkins test make check arm64 |
@@ -418,8 +418,6 @@ def teardown(self): | |||
""" | |||
super(FuseMount, self).teardown() | |||
|
|||
self.umount() | |||
|
|||
if self.fuse_daemon and not self.fuse_daemon.finished: | |||
self.fuse_daemon.stdin.close() | |||
try: |
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.
out of academic interest, shouldn't the base class teardown() happen after the derived class teardown() ?
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.
Yes. We live in a special circle of Python's Hell.
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
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.
We should backport this I think, yes? @batrick
I didn't think it necessarily needed backport. There shouldn't be a significant functional change. |
This PR is under test in https://tracker.ceph.com/issues/65530. |
This PR is under test in https://tracker.ceph.com/issues/65562. |
This PR is under test in https://tracker.ceph.com/issues/65596. |
Contribution Guidelines
To sign and title your commits, please refer to Submitting Patches to Ceph.
If you are submitting a fix for a stable branch (e.g. "quincy"), please refer to Submitting Patches to Ceph - Backports for the proper workflow.
When filling out the below checklist, you may click boxes directly in the GitHub web UI. When entering or editing the entire PR message in the GitHub web UI editor, you may also select a checklist item by adding an
x
between the brackets:[x]
. Spaces and capitalization matter when checking off items this way.Checklist
Show available Jenkins commands
jenkins retest this please
jenkins test classic perf
jenkins test crimson perf
jenkins test signed
jenkins test make check
jenkins test make check arm64
jenkins test submodules
jenkins test dashboard
jenkins test dashboard cephadm
jenkins test api
jenkins test docs
jenkins render docs
jenkins test ceph-volume all
jenkins test ceph-volume tox
jenkins test windows
jenkins test rook e2e