Description of problem: When deploying a new VM from simplified-installer.iso as described in https://github.com/osbuild/rhel-for-edge-demo and https://www.youtube.com/watch?v=_nq5IAVbl2Y the installation fails with error messages tcti:src/tss2-tcti/tctildr.c:416:Tss2_TctiLdr_Initialize_Ex() Failed to instantiate TCTI tss_esapi::tcti_ldr > Error when creating a TCTI context: response code not recognized right after the fdo_manufacturing_client is Performing DIUN. The VM is configured with the emulated TIS TPMv2.0 device. Looking at the fdo-aio logfiles, I would say the communication between the fdo services and the VM is working. Version-Release number of selected component (if applicable): Version : 0.4.7 Release : 3.el9 How reproducible: , Steps to Reproduce: 1. Create most simple simplified-installer.iso with the RHEL9 image builder 2. install fdo-admin-cli and provide with serviceinfo_api_server.yml from github rhel-for-edge-demo 3. deploy new VM with virt-install \ --name ${NAME} \ --description "${NAME} FDO Edge Instance" \ --os-type=Linux \ --os-variant=rhel9.2 \ --tpm backend.type=emulator,backend.version=2.0,model=tpm-tis \ --boot uefi \ --ram=3072 \ --vcpus=1 \ --disk path=/var/lib/libvirt/images/${NAME}.qcow2,bus=virtio,size=10 \ --network network=host-bridge,mac=52:54:00:0b:46:2f \ --location /srv/Images/ISO/simplified-installer.iso Actual results: Installation fails and journalctl shows tcti:src/tss2-tcti/tctildr.c:416:Tss2_TctiLdr_Initialize_Ex() Failed to instantiate TCTI tss_esapi::tcti_ldr > Error when creating a TCTI context: response code not recognized Expected results: Installation customized according to serviceinfo_api_server.yml Additional info:
We are tracking this upstream as well - https://github.com/fedora-iot/fido-device-onboard-rs/issues/531
PR with fix posted: https://github.com/fedora-iot/fido-device-onboard-rs/pull/536