iot-raw-image-f37 audit log record result failed

[mcattamoredhat]

After upgrading an image in iot-raw-image-f37, the playbook fails during dmesg checking. The following output shows an example of error message:

audit: type=1103 audit(1698231505.341:213): pid=949 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='op=PAM:setcred grantors=? acct="admin" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed'

Playbook task failing:

TASK [check dmesg error and fail log] ******************************************
changed: [192.168.100.51] => changed=true 
  cmd: dmesg --notime | grep -i "error\|fail" | grep -v "skipped" | grep -v "failover" | grep -v "ignition" | grep -v "BAR 13":" failed to assign" || true
  delta: '0:00:00.015745'
  end: '2023-10-25 10:58:46.441719'
  msg: ''
  rc: 0
  start: '2023-10-25 10:58:46.425974'
  stderr: ''
  stderr_lines: <omitted>
  stdout: |-
    RAS: Correctable Errors collector initialized.
    systemd[1]: bpf-lsm: Failed to load BPF object: No such process
    systemd[1]: bpf-lsm: Failed to load BPF object: No such process
    systemd-gpt-auto-generator[608]: Failed to dissect: Permission denied
    (sd-executor)[598]: /usr/lib/systemd/system-generators/systemd-gpt-auto-generator failed with exit status 1.
    audit: type=1103 audit(1698231505.341:213): pid=949 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='op=PAM:setcred grantors=? acct="admin" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=failed'
  stdout_lines: <omitted>


pcieport 0000:00:01.6: Failed to check link status
Error: Driver \\'pcspkr\\' is already registered, aborting
KD_FONT_OP_GET failed while trying to get the font metadata: Invalid argument
sys-module-fuse.device: Failed to enqueue SYSTEMD_WANTS= job, ignoring: Unit sys-fs-fuse-connections.mount not found
/usr/lib/systemd/system-generators/podman-system-generator failed with exit status 1

Complete output of workflow job: https://github.com/virt-s1/rhel-edge/actions/runs/6629578843/job/18034289907#step:4:8922

This issue is reproducible both in Openstack rhos-01 and GCP.

[mcattamoredhat]

A similar issue has been seen at workflow job