Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
DescriptionSebastian Hetze
2023-07-18 21:35:35 UTC
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: