NAS-133018 / 25.04 / Fix up test to match reality of NFS client reporting. #15244
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
NFS client reporting is not terribly deterministic.
NFSv3 client info can be found in
/var/db/system/nfs/rmtab
and inss
output. The info inrmtab
is notoriously inaccurate in that it's updated by the client viamount
andumount
commands. Since we currently do no clearrmtab
this nearly always results in stale entries. See https://ixsystems.atlassian.net/browse/NAS-131762NFSv4 clients are connection based, but they use a periodic refresh to remind the server of their presence and there is a call back to notify 'attached' clients. Thus, after an NFS server start it can take a second or two for all the clients to report their
status.
Passing test here: http://jenkins.eng.ixsystems.net:8080/job/tests/job/api_tests/2337/