Failures in these paladins look different. 

Maybe similar example in this build:

https://luci-milo.appspot.com/buildbot/chromeos/guado-paladin/3724

cfm_AutotestSmokeTest.DEBUG shows many repeats of the following:

06/21 10:17:34.665 DEBUG|    cros_interface:0058| sh -c cryptohome-path user 'test@test.test' 
06/21 10:17:34.666 DEBUG|      global_hooks:0056| ['sh', '-c', "cryptohome-path user 'test@test.test'"]
06/21 10:17:34.679 DEBUG|    cros_interface:0067|  > stdout=[/home/user/eeba2648d49c5705ae833a78708ce71a99206230
], stderr=[]
06/21 10:17:34.680 DEBUG|    cros_interface:0058| sh -c /bin/df --output=source,target /run/cryptohome/ephemeral_mount/eeba2648d49c5705ae833a78708ce71a99206230 
06/21 10:17:34.680 DEBUG|      global_hooks:0056| ['sh', '-c', '/bin/df --output=source,target /run/cryptohome/ephemeral_mount/eeba2648d49c5705ae833a78708ce71a99206230']
06/21 10:17:34.688 DEBUG|    cros_interface:0067|  > stdout=[], stderr=[df: /run/cryptohome/ephemeral_mount/eeba2648d49c5705ae833a78708ce71a99206230: No such file or directory
]


Ultimately terminating with:
06/21 10:32:42.058 ERROR|           browser:0054| Failed with LoginException while starting the browser backend.
06/21 10:32:42.655 ERROR|            chrome:0192| Timed out logging in, tries=0, error=LoginException('Timed out going through login screen. Cryptohome not mounted. OOBE not dismissed.',)

The following two builds have the same signature

https://luci-milo.appspot.com/buildbot/chromeos/auron_yuna-paladin/3268
https://luci-milo.appspot.com/buildbot/chromeos/veyron_minnie-paladin/6371


Looks like there are a couple of cryptohome CLs trying to make it through the CQ.

I should probably not be the owner of this since I'm not a cryptohome expert.

Gwendal, can you tell us who "owns" cryptohome support?

Looking, at the errors in #4, the proposed ACL changes in https://chromium-review.googlesource.com/c/chromiumos/platform2/+/1067297 is suspect.

CL abandoned.