Current situation
Now we can see the error logs of tss_esapi when using az-cvm-vtpm for platforms not supporting vtpm. See the link for example
ERROR:tcti:src/tss2-tcti/tcti-device.c:452:Tss2_Tcti_Device_Init() Failed to open specified TCTI device file /dev/tpm0: No such file or directory
ERROR:tcti:src/tss2-tcti/tctildr-dl.c:154:tcti_from_file() Could not initialize TCTI file: device
ERROR:tcti:src/tss2-tcti/tctildr.c:428:Tss2_TctiLdr_Initialize_Ex() Failed to instantiate TCTI
[2024-12-02T05:44:35Z ERROR tss_esapi::tcti_ldr] Error when creating a TCTI context: response code not recognized
ERROR:tcti:src/tss2-tcti/tcti-device.c:452:Tss2_Tcti_Device_Init() Failed to open specified TCTI device file /dev/tpm0: No such file or directory
ERROR:tcti:src/tss2-tcti/tctildr-dl.c:154:tcti_from_file() Could not initialize TCTI file: device
ERROR:tcti:src/tss2-tcti/tctildr.c:428:Tss2_TctiLdr_Initialize_Ex() Failed to instantiate TCTI
Impact
This would bring extra error information for users that sometimes confused.
Ideal future situation
Only raise a piece of log of error or warn level to indicate that underlying tpm/tss is not configured properly. Other logs could be put to trace or debug level.
Implementation options
None
Additional information
None
Current situation
Now we can see the error logs of
tss_esapiwhen usingaz-cvm-vtpmfor platforms not supporting vtpm. See the link for exampleImpact
This would bring extra error information for users that sometimes confused.
Ideal future situation
Only raise a piece of log of
errororwarnlevel to indicate that underlying tpm/tss is not configured properly. Other logs could be put totraceordebuglevel.Implementation options
None
Additional information
None