Skip to content

Conversation

@gman0
Copy link
Collaborator

@gman0 gman0 commented Sep 30, 2023

automount daemon unmounts the autofs root in /cvmfs upon receiving SIGTERM. This makes it impossible to reconnect the daemon to the mount later, so all consumer Pods will loose their mounts CVMFS, without the possibility of restoring them (unless these Pods are restarted too). The implication is that the nodeplugin is just being restarted, and will be needed again.

SIGKILL is handled differently in automount, as this forces the daemon to skip the cleanup at exit, leaving the autofs mount behind and making it possible to reconnect to it later. We make a use of this, and unless the admin doesn't explicitly ask for cleanup with AUTOFS_TRY_CLEAN_AT_EXIT env var, no cleanup is done.

Cherry-pick f1d7ee2 (#122)

automount daemon unmounts the autofs root in /cvmfs upon
receiving SIGTERM. This makes it impossible to reconnect
the daemon to the mount later, so all consumer Pods will
loose their mounts CVMFS, without the possibility of restoring
them (unless these Pods are restarted too). The implication
is that the nodeplugin is just being restarted, and will be
needed again.

SIGKILL is handled differently in automount, as this forces
the daemon to skip the cleanup at exit, leaving the autofs
mount behind and making it possible to reconnect to it later.
We make a use of this, and unless the admin doesn't explicitly
ask for cleanup with AUTOFS_TRY_CLEAN_AT_EXIT env var, no cleanup
is done.

Cherry-pick f1d7ee2 (cvmfs-contrib#122)
@gman0 gman0 changed the title automount: shut down automount daemon with SIGKILL (Backport #122) automount: shut down automount daemon with SIGKILL Sep 30, 2023
@gman0 gman0 merged commit d39df5a into cvmfs-contrib:release-2.3 Sep 30, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant