[multiple] Handle already-unlocked state in usroverlay task

rpm-ostree usroverlay returns exit code 1 with the message
"Deployment is already in unlocked state: development" when the
CoreOS node is already in the unlocked overlay state from a previous
run. This caused the pcp_metrics hook to abort the entire deployment
on re-runs without a full node reboot.

Register the result and only treat non-zero exit codes as failures
when the stderr does not contain the "already in unlocked state"
message, making the task idempotent across multiple deploy attempts.

Signed-off-by: Ade Lee <alee@redhat.com>
Co-Authored-By: Claude <noreply@anthropic.com>

Author: 2 people

roles/pcp_metrics/tasks/coreos.yaml

@@ -15,6 +15,12 @@
   become: true
   ansible.builtin.command:
     cmd: rpm-ostree usroverlay
+  register: _pcp_usroverlay
+  changed_when: _pcp_usroverlay.rc == 0
+  failed_when:
+    - _pcp_usroverlay.rc != 0
+    - >-
+      "already in unlocked state" not in _pcp_usroverlay.stderr
 
 - name: Create required directory
   become: true