mount_setup
Maintains the ansible/roles/mount_setup Ansible role that enables or disables filesystem mounts (local or NFS/CIFS) via /etc/fstab, as part of the Linux SOE. Use when checking or fixing mount/fstab st
SKILL.md.claude/skills/mount_setup/SKILL.md
GitHubmount_setup
Maintains ansible/roles/mount_setup/. See docs/ARCHITECTURE.md for the shared
conventions (role layout, audit vs. remediate via --check --diff, safety
rules, branch + PR contribution workflow).
ansible/roles/mount_setup/README.md documents this role's full
configuration surface (every defaults/main.yml variable, with its
original inline comments, rendered as a single reference). Read it
before proposing or explaining how to configure this role — it
reflects the role's actual current defaults even if a variable summary
elsewhere in this file has drifted out of sync with the role.
Policy & workload awareness
docs/VERTICAL_POLICY.md, docs/HORIZONTAL_POLICY and docs/WORKLOAD.md capture org-wide policy items and
the workloads this SOE actually hosts — either can gain a new or changed
item that this role should reflect. Before auditing, remediating, or
proposing a change, check whether either doc has changed more recently
than this role's own code:
git log -1 --format='%cI %h %s' -- docs/VERTICAL_POLICY.md docs/HORIZONTAL_POLICY.md docs/WORKLOAD.md
git log -1 --format='%cI %h %s' -- ansible/roles/mount_setup/
If the docs' latest commit is newer than the role's, this role hasn't been re-assessed against current policy/workload — read both files and judge whether anything added or changed since is relevant to this domain:
- Relevant — propose a concrete change on a branch
(
soe/mount_setup/policy-<short-desc>orsoe/mount_setup/workload-<short-desc>), same branch + PR workflow as any other role change (see "What to do" above anddocs/ARCHITECTURE.md's "Contribution workflow"). Don't wait to be asked. - Not relevant — say so explicitly (e.g. "checked against
docs/VERTICAL_POLICY.md,docs/HORIZONTAL_POLICYanddocs/WORKLOAD.mdas of<date>, nothing affecting this domain") rather than silently skipping the check.
This check is informational, not a gate — it runs alongside a normal audit/remediate, never blocks one; surface the staleness note alongside the normal output.
What the role actually does
Encoded in ansible/roles/mount_setup/defaults/main.yml:
mount_setup_disableandmount_setup_enableboth default empty — no-op until set. Entries useansible.posix.mountfields directly (src,path,state,fstype,opts, etc.).- Installs
nfs-utils/cifs-utilsautomatically, only if anmount_setup_enableentry'sfstypeneeds them. - An entry present in both lists is treated as "enable wins" — disable is
skipped for any path also in
mount_setup_enable.
This role is sourced from the myllynen/rhel-ansible-roles import
(see git log -- ansible/roles/mount_setup) rather than hand-authored for this
repo. Unlike the original reference domains (e.g. timesync, usbguard_setup),
it applies state declaratively via standard Ansible modules and does not
add its own assert-based drift checks on top — an audit here is exactly
what --check --diff reports from the underlying modules, nothing more.
What to do
NFS client hosts — ansible/nfs_client_setup.yml sets
mount_setup_enable for nfs_mount_src/nfs_mount_dir and is the normal
way to run this role:
ansible-playbook ansible/nfs_client_setup.yml --tags mount_setup --check --diff # audit
ansible-playbook ansible/nfs_client_setup.yml --tags mount_setup # remediate
Summarize the diff output and any failed tasks in plain language, and only
drop --check after the user explicitly asks.
Any other host — the role is present in
ansible/configure_rhel.yml's roles: list, gated by
configure_rhel_domains (off by default — see
.claude/skills/configure_rhel/SKILL.md); it's a no-op there today. Add
mount_setup to configure_rhel_domains via -e (no file edit needed)
and set mount_setup_enable/mount_setup_disable for that host/group
before ansible-playbook ansible/configure_rhel.yml --tags mount_setup
will do anything.
Propose a change to the role itself: never edit and commit directly. On a
branch named soe/mount_setup/<short-desc>, edit ansible/roles/mount_setup/, validate
locally (--syntax-check, ansible-lint roles/mount_setup/, and
--check --diff against a real/test host if available), then push and open a
PR titled [mount_setup] <what changed> with the --check --diff output in the
body. Then stop — a human reviews and merges; see docs/ARCHITECTURE.md's
"Contribution workflow".
Wiring into the SOE
This role has a row in .claude/skills/soe/SKILL.md's domain table. It's
active by default only via ansible/nfs_client_setup.yml; it's present in
ansible/configure_rhel.yml's roles: list but off by default there
(not in configure_rhel_domains's default value — see
.claude/skills/configure_rhel/SKILL.md), so a plain, untagged
ansible-playbook ansible/configure_rhel.yml run does not touch mounts on
a general-purpose host. This repo no longer uses ansible/site.yml; see
docs/ARCHITECTURE.md.