From b9dfb40717a411012391236d96d2415adc20ae78 Mon Sep 17 00:00:00 2001 From: David Galloway Date: Fri, 28 Feb 2025 13:55:16 -0500 Subject: [PATCH] ansible: Fixes to podman subuid/subgid checks I think this was working during my testing because sub{u,g}id_check.rc /wasn't/ 0. I had manually modified the system so it wasn't in the same state as a fresh cloud instance. I manually ran this playbook on an instance and confirmed it gets past the podman setup now. Signed-off-by: David Galloway --- ansible/examples/builder.yml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/ansible/examples/builder.yml b/ansible/examples/builder.yml index 9d74326b..62aa573d 100644 --- a/ansible/examples/builder.yml +++ b/ansible/examples/builder.yml @@ -501,9 +501,9 @@ changed_when: false - name: Find highest used subuid - command: "awk -F: '{print $2+$3}' /etc/subuid | sort -n | tail -1" + shell: "awk -F: '{print $2+$3}' /etc/subuid | sort -n | tail -1" register: highest_subuid - when: subuid_check.rc != 0 or subgid_check.rc != 0 + when: subuid_check.rc == 0 or subgid_check.rc == 0 changed_when: false - name: Set next available UID range -- 2.47.3