system_hostname

Maintains ansible/roles/system_hostname/. See docs/ARCHITECTURE.md for the shared conventions (role layout, audit vs. remediate via --check --diff, safety rules, branch + PR contribution workflow).

ansible/roles/system_hostname/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/system_hostname/

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/system_hostname/policy-<short-desc> or soe/system_hostname/workload-<short-desc>), same branch + PR workflow as any other role change (see "What to do" above and docs/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_POLICY and docs/WORKLOAD.md as 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/system_hostname/defaults/main.yml:

• system_hostname defaults to ansible_facts.fqdn | lower — i.e. by default the role converges the host onto whatever its own current FQDN fact already resolves to (a near-no-op unless overridden), not a fleet-wide fixed value. Per the role's own comment: short name is generally preferred with DHCP, FQDN with static IP, and the max length is 63 characters.

This role is sourced from the myllynen/rhel-ansible-roles import (see git log -- ansible/roles/system_hostname) 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

This role is off by default in ansible/configure_rhel.yml — every role there (active or not) is gated by a single configure_rhel_domains list variable (when: "'<name>' in configure_rhel_domains"), and system_hostname isn't in the default value of that list. Nothing needs editing in the playbook itself to turn it on: pass the full desired domain list via -e, e.g. -e '{"configure_rhel_domains": [...the default 20..., "system_hostname"]}' (see .claude/skills/configure_rhel/SKILL.md for the current default list to extend, and why it has to be the full list, not just the addition — -e replaces the variable's value, it doesn't merge into it). --tags system_hostname alone is not enough — the domains list and --tags/--skip-tags are separate, ANDed gates, both verified independently: a role only runs if it's in configure_rhel_domains and matches the requested tags. Some roles (this one — check its defaults/main.yml and task file) also have their own internal enable flag or required variable on top of that, which still needs setting the same as before. Flag all of this to the user before assuming the commands below will do anything.

Audit (read-only, safe to run any time):

ansible-playbook ansible/configure_rhel.yml --tags system_hostname --check --diff

Summarize the diff output and any failed tasks in plain language.

Remediate (modifies the system — only after the user explicitly asks): first summarize what will change from the --check --diff output, then run the same command without --check:

ansible-playbook ansible/configure_rhel.yml --tags system_hostname

Propose a change to the role itself: never edit and commit directly. On a branch named soe/system_hostname/<short-desc>, edit ansible/roles/system_hostname/, validate locally (--syntax-check, ansible-lint roles/system_hostname/, and --check --diff against a real/test host if available), then push and open a PR titled [system_hostname] <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 present (not commented out) in ansible/configure_rhel.yml's roles: list, gated by configure_rhel_domains — off by default, on via -e — see the caveat at the top of "What to do" above and .claude/skills/configure_rhel/SKILL.md. It is not referenced by any of the other playbooks (load_balancer_setup.yml, nfs_client_setup.yml, nfs_server_setup.yml, update_rhel.yml, connect_linux.yml) either. This repo no longer uses ansible/site.yml; see docs/ARCHITECTURE.md.