From a165a79f953d2a6900624ce4fc7ef8f6b7b42e8e Mon Sep 17 00:00:00 2001 From: cproudlock Date: Sun, 14 Jun 2026 10:12:06 -0400 Subject: [PATCH] imaging: force shopfloor unattend deploy (was force:no -> went stale) The shopfloor unattend deploy used force:no, so once a live copy existed the playbook never overwrote it. That let the live gea-shopfloor unattend drift for weeks - missing the Fetch + Verify-And-Heal staging steps - which is why imaging lost payloads (CMM bundle/backups). Flip to force:yes so the repo stays the source of truth, matching the standard/engineer unattend task. Co-Authored-By: Claude Opus 4.8 (1M context) --- playbook/pxe_server_setup.yml | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/playbook/pxe_server_setup.yml b/playbook/pxe_server_setup.yml index 05352c5..c9109b9 100644 --- a/playbook/pxe_server_setup.yml +++ b/playbook/pxe_server_setup.yml @@ -685,7 +685,11 @@ src: "{{ usb_mount }}/FlatUnattendW10-shopfloor.xml" dest: "{{ samba_share }}/{{ item }}/Deploy/FlatUnattendW10.xml" mode: '0644' - force: no + # force: yes - repo is source of truth. force: no let the live shopfloor + # unattend go stale (missing the Fetch + Verify-And-Heal staging steps), + # and a playbook run never repaired it. Keep it in sync like the standard + # /engineer unattend below. + force: yes loop: "{{ shopfloor_types }}" ignore_errors: yes