New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 872444 link

Starred by 1 user
Status: Duplicate
Owner:
█ jkop@chromium.org
Last visit > 30 days ago
Closed: Aug 8
Cc:
█ jmuppala@chromium.org
briannorris@chromium.org
█ jkop@chromium.org
█ anmarroquin@chromium.org
█ dschimmels@chromium.org
█ jashur@chromium.org
aashuto...@chromium.org
dsunk...@chromium.org
dchan@chromium.org
█ jrbarnette@chromium.org
█ kirtika@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug



Sign in to add a comment

Majority of the devices in wifi labs are in repair failed or repairing state

Project Member Reported by harpreet@chromium.org, Aug 8 
~40 devices in wifi lab are in repair failed or repairing state for the last few days. All these devices were previously running as expected.

chromeos15-row1-rack10-host4	setzer	Repairing
chromeos15-row1-rack9-host2	lars	Repairing
chromeos15-row1-rack9-host4	celes	Repairing
chromeos15-row1-rack5-host1	peppy	Repairing
chromeos15-row1-rack5-host3	big	Repairing
chromeos15-row1-rack5-host4	lulu	Repairing
chromeos15-row1-rack1-host5	basking	Repairing
chromeos15-row1-rack5-host5	celes	Repairing
chromeos15-row1-rack7-host5	cave	Repairing
chromeos15-row1-rack2-host3	teemo	Repairing
chromeos15-row1-rack2-host2	blacktip	Repairing
chromeos15-row1-rack7-host6	pyro	Repairing
chromeos15-row1-rack8-host4	veyron_mighty	Repairing
chromeos15-row1-rack5-host7	veyron_minnie	Repairing
chromeos15-row4-rack12-host5	blue	Repairing
chromeos15-row4-rack12-host6	bruce	Repairing
chromeos15-row4-rack12-host4	babymega	Repairing
chromeos15-row1-rack10-host6	bob	Repairing
chromeos15-row2-rack2-host1	yuna	Repairing
chromeos15-row2-rack2-host3	monroe	Repairing
chromeos15-row4-rack12-host7	scarlet	Repairing
chromeos5-row1-rack3-host3	kevin	Repairing
chromeos15-row1-rack5-host2	spring	Repair Failed
chromeos15-row1-rack8-host6	sand	Repair Failed
chromeos15-row4-rack12-host2	grunt	Repair Failed
chromeos15-row4-rack12-host3	sona	Repair Failed
chromeos15-row1-rack2-host7	nautilus	Repair Failed
chromeos15-row4-rack11-host2	pantheon	Repair Failed
chromeos15-row3-rack9-host1	snow	Repair Failed
chromeos15-row3-rack9-host4	kevin	Repair Failed
chromeos15-row3-rack9-host5	chell	Repair Failed
chromeos15-row3-rack9-host6	elm	Repair Failed
chromeos15-row3-rack10-host6	jaq	Repair Failed
chromeos5-row1-rack3-host2	elm	Repair Failed
chromeos5-row1-rack3-host4	lulu	Repair Failed


Example logs...
chromeos15-row1-rack7-host5 cave - 
https://stainless.corp.google.com/browse/chromeos-autotest-results/hosts/chromeos15-row1-rack7-host5/1816932-repair/20180808114755/
https://storage.cloud.google.com/chromeos-autotest-results/hosts/chromeos15-row1-rack7-host5/1816932-repair/20180808114755/debug/autoserv.DEBUG


chromeos15-row4-rack12-host6 bruce -
https://stainless.corp.google.com/browse/chromeos-autotest-results/hosts/chromeos15-row4-rack12-host6/2429461-repair/
https://storage.cloud.google.com/chromeos-autotest-results/hosts/chromeos15-row4-rack12-host6/2429461-repair/20180708220312/debug/autoserv.DEBUG

Comment 1 by jrbarnette@chromium.org, Aug 8

Components: -Infra>Client>ChromeOS Infra>Client>ChromeOS>Test
DUT chromeos15-row1-rack7-host5 is bug 872033.

I'm not sure what's up with chromeos15-row4-rack12-host6; it could be
the same thing, or there could be something else going on.  If it's
"something else" the first place to look would be the DUT.

Why is this assigned to xixuan@ instead of to this week's deputy?

Comment 2 by xixuan@chromium.org, Aug 8

Owner: jkop@chromium.org
Re-assign to deputy. It'S also in lab chromeos15.

Comment 3 by harpreet@chromium.org, Aug 8

Mergedinto: 872033
Status: Duplicate (was: Assigned)
OK. I am going to merge this into that issue. chromeos15-row4-rack12-host6 could be related. So lets first resolve crbug/872033 and see if that fixes all the DUTs in chromeos15.

Comment 4 by kirtika@chromium.org, Aug 9 

this does not seem wifi related - can you check (1) if other lab devices have similar issues (2) what OS version were they running when they got borked?
I noticed there were mosys bugs on ToT recently that could do things like prevent booting from usb or booting in recovery mode. Specifically, I want to confirm OS version >= 10933.0.0 (mosys seccomp issue should be fixed).
►

Sign in to add a comment