Bug #56476
Updated by Rishabh Dave almost 2 years ago
In "@4-compat_client.yaml@":https://github.com/ceph/ceph/blob/main/qa/suites/fs/upgrade/featureful_client/upgraded_client/tasks/4-compat_client.yaml creates two clients, evicts one of them but the evicted client is left unhandled which leads to failure for final teardown -
<pre>
- fs.clients_evicted:
clients:
client.0: False
client.1: True
</pre>
The This evicted client is not cleaned up later, that is, it is left unmounted and the mount point is left undeleted. This doesn't cause any failure remains in a hanged state which can be problematic during final teardown for main branch but, with PR #45036, it does lead to the teuthology job.
This problem was repeatedly seen for teuthology job failures every time.
With for PR #45036, the "qa/cephfs" https://github.com/ceph/ceph/pull/45036 because this PR adds code does not depend (anymore) on the value of the attribute "is_mounted" to check that actually checks if a CephFS has been unmounted or not. Instead, delete the attribute "is_mounted" it and runs the command "findmnt <mntpt>" to check if the client was actually unmounted from instead by running @sudo findmnt <mntpt>@. This command hangs when the system's FS.
Operating on a CephFS mount point after the client has been evicted causes which owns the operation to hang. Thus, with PR #45036, the final teardown for this teuthology job fails every time. mountpoint hangs.
The fix for this is too run @umount -f@ for the mountpoint of evicted client and delete the mountpoint. Then, final teardown will run fine with PR #45036 too. fine.