tests: add check that removal of snaps works with user data #14053
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.
Test adds check to see if https://bugs.launchpad.net/snapd/+bug/2002697 is easily reproducible when using home directories exported via NFSv3 or NFSv4.
This issue is easily reproducible on HPC deployments where NFS is used as the shared filesystem for exporting data across the cluster. Snaps can be installed and used by "remote users" - defined in LDAP and not in /etc/passwd - but they cannot be refreshed an/or removed when
root_squash
is enabled as snapshottingSNAP_USER_DATA
andSNAP_USER_COMMON
is disallowed by the filesystem.