ansible-playbooks/.project-wiki/alerts/ALERT-20260909-002.md

id, type, status, severity, title, created, updated, resolved, tags, related, source_paths, confidence

id	type	status	severity	title	created	updated	resolved	tags	related	source_paths	confidence
ALERT-20260909-002	alert	resolved	medium	Uncommitted dmc12-to-cloudlorean rename and stale documentation	2026-09-09	2026-09-09	2026-09-09	alert consistency git	OQ-003 SCAN-20260909 TECH-CODEBASE-MAP	inventory/dmc12.yml inventory/cloudlorean.yml inventory/group_vars/cloudlorean.yml README.md AGENTS.md	confirmed

ALERT-20260909-002 - Uncommitted dmc12-to-cloudlorean rename and stale documentation

Summary

The working tree carries a large uncommitted change set (23 modified files, 203 insertions / 148 deletions) including the deletion of inventory/dmc12.yml and the addition of untracked inventory/cloudlorean.yml + inventory/group_vars/cloudlorean.yml (git log confirms no rename commit). README.md (inventory table, call examples) and AGENTS.md (fallstricke) still reference inventory/dmc12.yml and group_vars/dmc12.yml, which no longer exist.

Why It Matters

• Documentation, examples, and agent instructions point to a non-existent inventory; commands copied from README fail.
• The rename plus modifications exist only in the working tree; losing or partially committing them would leave the repo internally inconsistent.
• Git history will not record a rename (delete + untracked add), which complicates tracing inventory history.

Evidence

• git status --short: D inventory/dmc12.yml, ?? inventory/cloudlorean.yml, ?? inventory/group_vars/cloudlorean.yml, plus modified roles/ansible.cfg/ execute.sh/README/AGENTS
• git log --follow -- inventory/dmc12.yml: only add commit d2e8ce4
• README.md inventory table lists dmc12.yml / group_vars/dmc12.yml
• logs/cloudlorean/dmc12/ and .zabbix-psk/dmc12.psk exist for host dmc12 under the new site name

Suggested Resolution

1. Update README.md and AGENTS.md to the cloudlorean inventory.
2. Review and commit the rename together with the modified files as one coherent change (owner decision).

Resolution

Resolved 2026-09-09 (owner decision confirmed during the session):

1. Documentation updated to the cloudlorean inventory:
   • README.md - inventory table (Cloudlorean row: cloudlorean.yml / group_vars/cloudlorean.yml + debian.yml), all call examples, "Secrets & Vault" example command.
   • AGENTS.md - "Häufige Fallstricke": ssh_service_name reference now points to inventory/cloudlorean.yml (gitea, ipam).
   • Role READMEs (bootstrap, monitoring, docker, os-updates, healthcheck, manage-ssh-keys, hawser): all inventory/dmc12.yml call examples replaced with inventory/cloudlorean.yml.
2. The rename and the full working-tree change set (23 modified files, untracked inventory/cloudlorean.yml + inventory/group_vars/ cloudlorean.yml, plus this resolution's documentation/vault fixes) were committed together as one coherent change, as suggested.

Resolution Evidence

• rg -n "dmc12\.yml" across README.md, AGENTS.md, and roles/ returns no matches.
• git status --short is clean after the commit 30f3e9a ("rename dmc12 inventory to cloudlorean and vault admin_password", 2026-09-09); the change set - including the inventory rename and this resolution - is recorded as one commit.
• README inventory table lists Cloudlorean with group_vars/cloudlorean.yml and debian.yml, matching inventory/ contents.