New issue
Advanced search Search tips

Issue 878889 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner: ----
Closed: Oct 24
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: ----



Sign in to add a comment

betty-arc64-paladin:3378 failed

Project Member Reported by sheriff-...@appspot.gserviceaccount.com, Aug 29

Issue description

Some errors reported by cryptohome.  Unclear if this is because there is no TPM on this system

2018-08-29T12:16:41.085412-05:00 ERR cryptohomed[2378]: TPM error 0x3011 (Communication failure): Error calling Tspi_Context_Connect
2018-08-29T12:16:41.085725-05:00 ERR cryptohomed[2378]: ConnectContextAsUser: Could not open the TPM
2018-08-29T12:16:41.085754-05:00 ERR cryptohomed[2378]: ReadPCR: Failed to connect to the TPM.
2018-08-29T12:16:41.085780-05:00 WARNING cryptohomed[2378]: Failed to read PCR1.
2018-08-29T12:16:41.085946-05:00 ERR cryptohomed[2378]: stat() of /mnt/stateful_partition/unencrypted/preserve/attestation.epb failed.: No such file or directory
2018-08-29T12:16:41.086149-05:00 ERR cryptohomed[2378]: Failed to read db.: No such file or directory
2018-08-29T12:16:41.086188-05:00 INFO cryptohomed[2378]: Attestation: Attestation data not found.
2018-08-29T12:16:42.089179-05:00 ERR cryptohomed[2378]: TPM error 0x3011 (Communication failure): Error calling Tspi_Context_Connect
2018-08-29T12:16:42.089363-05:00 ERR cryptohomed[2378]: Could not open the TPM
2018-08-29T12:16:43.091355-05:00 ERR cryptohomed[2378]: TPM error 0x3011 (Communication failure): Error calling Tspi_Context_Connect
2018-08-29T12:16:43.091521-05:00 ERR cryptohomed[2378]: Could not open the TPM
2018-08-29T12:16:43.091546-05:00 ERR cryptohomed[2378]: GetRandomDataBlob failed
2018-08-29T12:16:43.091589-05:00 ERR cryptohomed[2378]: Could not get random data from the TPM
2018-08-29T12:16:43.091612-05:00 ERR cryptohomed[2378]: FAILED TO SEED /dev/urandom AT START
2018-08-29T12:16:44.093905-05:00 ERR cryptohomed[2378]: TPM error 0x3011 (Communication failure): Error calling Tspi_Context_Connect
2018-08-29T12:16:44.094236-05:00 ERR cryptohomed[2378]: ConnectContextAsUser: Could not open the TPM
2018-08-29T12:16:44.094292-05:00 ERR cryptohomed[2378]: GetEndorsementPublicKey: Could not connect to the TPM.
2018-08-29T12:16:44.094377-05:00 WARNING cryptohomed[2378]: TPM is not owned but failed to cache EK public key.
2018-08-29T12:16:44.095167-05:00 INFO cryptohomed[2378]: Cannot read boot lockbox files.
2018-08-29T12:16:44.095404-05:00 INFO cryptohomed[2378]: The TPM chip does not support GetAlertsData. Stop UploadAlertsData task.
2018-08-29T12:16:44.096835-05:00 INFO cryptohomed[2378]: Configuring TPM, ownership taken: 0.

(also took a look at it)

For build 3377, the same test (vm_test / login_OwnershipApi) passes, but shows the same cryptohome messages.

https://cros-goldeneye.corp.google.com/chromeos/healthmonitoring/buildDetails?buildbucketId=8936870226444752496

I'm not sure why it rebooted.

Since this was a VM test, I wonder if there might have been something helpful in the qemu logs (if any?), but I didn't find them.

ran the tests locally, cryptohome errors seem to be a red herring.
 Issue 878888  has been merged into this issue.
Status: WontFix (was: Available)
Green for days. Closing

Sign in to add a comment