New issue
Advanced search Search tips

Issue 902067 link

Starred by 3 users

Issue metadata

Status: Assigned
Owner:
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug



Sign in to add a comment

Container mounting fails sometimes

Project Member Reported by jkardatzke@google.com, Nov 5

Issue description

Last seen in Chrome OS 11231.0.0 on kevin.

Test results here: https://stainless.corp.google.com/browse/chromeos-autotest-results/255436288-chromeos-test/

This is what's in messages at the time:

2018-11-05T16:50:00.625545+00:00 INFO VM(3)[7869]:  lxd[170]: alias=debian/stretch image=5331b13df31be0367e62e20d4514947b74590d65f4b7158fbc0a1288d4294e25 lvl=info msg="Image downloaded" operation=1af4509d-bf7e-4acc-826f-61b4801cf21c server=https://storage.googleapis.com/cros-containers t=2018-11-05T16:49:57+0000 trigger=/1.0/operations/1af4509d-bf7e-4acc-826f-61b4801cf21c#012
2018-11-05T16:50:00.625567+00:00 INFO VM(3)[7869]:  lxd[170]: ephemeral=false lvl=info msg="Creating container" name=penguin t=2018-11-05T16:49:57+0000#012
2018-11-05T16:50:00.651148+00:00 INFO kernel: [ 1206.870378] CPU4: update max cpu_capacity 914
2018-11-05T16:50:01.239165+00:00 INFO kernel: [ 1207.458376] CPU4: update max cpu_capacity 1024
2018-11-05T16:50:01.835162+00:00 WARNING kernel: [ 1208.056111] cpu_cooling_ratelimit: 68 callbacks suppressed
2018-11-05T16:50:01.835187+00:00 INFO kernel: [ 1208.056125] cpu cpu4: Cooling state set to 1. New max freq = 1800000
2018-11-05T16:50:01.840147+00:00 INFO kernel: [ 1208.059485] CPU4: update max cpu_capacity 914
2018-11-05T16:50:02.042145+00:00 INFO kernel: [ 1208.261376] CPU4: update max cpu_capacity 1024
2018-11-05T16:50:02.242158+00:00 INFO kernel: [ 1208.461799] CPU4: update max cpu_capacity 914
2018-11-05T16:50:02.357165+00:00 INFO kernel: [ 1208.577164] CPU4: update max cpu_capacity 1024
2018-11-05T16:50:02.544208+00:00 INFO kernel: [ 1208.765384] CPU4: update max cpu_capacity 914
2018-11-05T16:50:02.646027+00:00 INFO kernel: [ 1208.864584] CPU5: update max cpu_capacity 1024
2018-11-05T16:50:03.244153+00:00 INFO kernel: [ 1209.463970] CPU5: update max cpu_capacity 914
2018-11-05T16:50:03.386848+00:00 INFO VM(3)[7904]: [   59.861147] maitred: <unknown process> (251) killed by signal 9#015
2018-11-05T16:50:04.278733+00:00 INFO VM(3)[7904]: [   60.753877] maitred: <unknown process> (310) exited with status 0#015
2018-11-05T16:50:05.041793+00:00 INFO vm_concierge[7877]: Shutting down due to SIGTERM
2018-11-05T16:50:05.078006+00:00 INFO VM(3)[7869]:  lxd[170]: lvl=info msg="Dqlite: closing client" t=2018-11-05T16:50:03+0000#012
2018-11-05T16:50:05.078030+00:00 INFO VM(3)[7869]:  lxd[170]: lvl=info msg="Dqlite: handling new connection (fd=24)" t=2018-11-05T16:50:03+0000#012
2018-11-05T16:50:05.078039+00:00 INFO VM(3)[7869]:  lxd[170]: lvl=info msg="Dqlite: connected address=0 attempt=0" t=2018-11-05T16:50:03+0000#012
2018-11-05T16:50:05.078046+00:00 INFO VM(3)[7869]:  lxd[170]: created=2018-11-05T16:49:57+0000 ephemeral=false lvl=info msg="Deleting container" name=penguin t=2018-11-05T16:50:03+0000 used=1970-01-01T00:00:00+0000#012

And then this will show up in the UI log:

[6951:6951:1105/085004.390417:ERROR:crostini_manager.cc(240)] Failed to Create Lxd Container.
[6951:6951:1105/085004.390652:ERROR:crostini_installer_view.cc(453)] Failed to mount container with error code: 12

 
Components: OS>Systems>Containers

Sign in to add a comment