New issue
Advanced search Search tips

Issue 888037 link

Starred by 2 users

Issue metadata

Status: WontFix
Owner:
Closed: Oct 4
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug



Sign in to add a comment

tast-tests failing due to SetUpUser RPC timeout

Project Member Reported by jkardatzke@chromium.org, Sep 21

Issue description

I'm seeing this in a number of test runs from last night fail against R71-11086 with similar signatures like this:

2018-09-21T09:24:13.787160-07:00 INFO VM(3)[20540]:  lxd[119]: action=start created=2018-09-21T16:21:22+0000 ephemeral=false lvl=info msg="Starting container" name=penguin stateful=false t=2018-09-21T16:24:10+0000 used=1970-01-01T00:00:00+0000#012
2018-09-21T09:24:13.940837-07:00 INFO vm_cicerone[20541]: Received SetUpLxdContainerUser request
2018-09-21T09:24:14.298835-07:00 INFO VM(3)[20562]: [  288.345722] new mount options do not match the existing superblock, will be ignored#015
2018-09-21T09:24:18.788824-07:00 INFO VM(3)[20540]:  lxd[119]: action=start created=2018-09-21T16:21:22+0000 ephemeral=false lvl=info msg="Started container" name=penguin stateful=false t=2018-09-21T16:24:13+0000 used=1970-01-01T00:00:00+0000#012
2018-09-21T09:24:18.788833-07:00 INFO VM(3)[20540]:  tremplin[140]: 2018/09/21 16:24:13 Received SetUpUser RPC: penguin (username testuser)#012
2018-09-21T09:24:28.960613-07:00 ERR vm_cicerone[20541]: SetUpUser RPC failed: Deadline Exceeded
2018-09-21T09:24:29.813115-07:00 INFO vm_concierge[20550]: Shutting down due to SIGTERM
 
These errors only occurred during the vm.CrostiniFiles test...they did not occur during vm.CrostiniStartEverything. (but the timeout was in cicerone, not in Chrome, so not sure why there's a difference there)
Labels: -Pri-2 M-71 Pri-1
Status: Started (was: Assigned)
I've seen this happening frequently on ToT as well.
Cc: dverkamp@chromium.org dgreid@chromium.org
vm.CrostiniStartEverything is using raw disks instead of qcow2. I suspect that we were borderline on the RPCs before, and some of the recent block device changes may have pushed us over the edge.

In the meantime, I'll increase the timeouts on these RPCs.
Status: WontFix (was: Started)
Should have been resolved by Jeff's timeout increase CLs.

Sign in to add a comment