You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While trying to see if we have a programmatic way to determine if a TPM exists on a machine, I looked at the TPM jobs in the base provider. I discovered that in providers/base/units/tpm/ there's a sysfs.pxu that lists several jobs that are supposed to get data from sysfs about installed TPMs.
Several of those seem to depend on a script called tpm_sysfs_resource.py, but that script does not seem to exist in checkbox.
unit: job
id: sysfs_tpm_count
category_id: tpm
plugin: resource
_summary: Count the number of visible TPM chips in sysfs
_description:
This job just counts the number of visible TPM chips in as reported by
tpm_sysfs_resource.py tool. The only resource attribute is 'count'
command: echo "count: $(tpm_sysfs_resource.py | grep -c -F 'x-sysfs-device-name')"
estimated_duration: 2s
flags: preserve-locale
How are these jobs ever run if that script doesn't exist? Is it stored somewhere outside of checkbox, perhaps?
To Reproduce
Review the info in the summary
The jobs all seem to call a non-existant script
Environment
Ubuntu, checkbox
Relevant log output
See description for output
Additional context
No response
The text was updated successfully, but these errors were encountered:
Bug Description
While trying to see if we have a programmatic way to determine if a TPM exists on a machine, I looked at the TPM jobs in the base provider. I discovered that in providers/base/units/tpm/ there's a sysfs.pxu that lists several jobs that are supposed to get data from sysfs about installed TPMs.
Several of those seem to depend on a script called tpm_sysfs_resource.py, but that script does not seem to exist in checkbox.
For example:
How are these jobs ever run if that script doesn't exist? Is it stored somewhere outside of checkbox, perhaps?
To Reproduce
Review the info in the summary
The jobs all seem to call a non-existant script
Environment
Ubuntu, checkbox
Relevant log output
See description for output
Additional context
No response
The text was updated successfully, but these errors were encountered: