What were you trying to do that didn't work?

Trying to initialize a device against a FDO manufacturing server.

The device is a VM booted into a simplified RHEL for Edge installer image. The FDO servers are running on RHEL 9.4, the simplified installer image was generated on the same machine.

Please provide the package NVR for which bug is seen:

fdo-manufacturing-client 0.5.0

Server side:

fdo-admin-cli.x86_64                             0.5.0-2.el9                         @rhel-9-for-x86_64-appstream-rpms
fdo-client.x86_64                                0.5.0-2.el9                         @rhel-9-for-x86_64-appstream-rpms
fdo-init.x86_64                                  0.5.0-2.el9                         @rhel-9-for-x86_64-appstream-rpms
fdo-manufacturing-server.x86_64                  0.5.0-2.el9                         @rhel-9-for-x86_64-appstream-rpms
fdo-owner-cli.x86_64                             0.5.0-2.el9                         @rhel-9-for-x86_64-appstream-rpms
fdo-owner-onboarding-server.x86_64               0.5.0-2.el9                         @rhel-9-for-x86_64-appstream-rpms
fdo-rendezvous-server.x86_64                     0.5.0-2.el9                         @rhel-9-for-x86_64-appstream-rpms

How reproducible:

Always

Steps to reproduce

1. Install FDO servers on a RHEL 9.4.0 machine.
2. Generate a simplified installer image (I was using `infra.osbuild` Ansible collection).
3. Boot a VM into the simplified installer ISO. Example:

  sudo virt-install \
    --boot uefi --network default \
    --name fdo-device --memory 2048 --vcpus 2 \
    --disk size=30,path=fdo-device.qcow2 \
    --os-variant rhel9.4 \
    --tpm backend.type=emulator,backend.version=2.0,model=tpm-tis \
    --cdrom fdo-demo_edge-simplified-installer.iso

Expected results

The device calls the manufacturing server and gets initialized successfully. An OV is created on the server side, a device-credentials file is created on the device.

Actual results

The manufacturing client seems to crash. The journal for the client shows

fdo_manufacturing_client > Performing DIUN

and some time after that 

Main process exited, code=killed, status=15/TERM

If I break into the emergency shell (install argument `coreos.inst.skip_reboot`) and restart the manufacturing client manually (`systemctl restart manufacturing-client`), the initialization seems to finish successfully. I can see an OV generated on the manufacturer server side, and a `/bootmount/device-credentials` file is created on the device.