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

Issue 822735 link

Starred by 1 user
Status: Fixed
Owner:
█ jrbarnette@chromium.org
Last visit > 30 days ago
Closed: Mar 2018
Cc:
dgarr...@chromium.org
jclinton@chromium.org
shapiroc@chromium.org
█ bhthompson@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug



Sign in to add a comment

Does arc label need to be removed from veyron_mickey boards?

Project Member Reported by derat@chromium.org, Mar 16 2018 
The ui.ARCSanity Tast test is failing when it runs on veyron_mickey:

2018/03/16 06:53:40 [06:53:39.264] Error at arc_sanity.go:23: Failed to connect to Chrome: missing Android image dir /opt/google/containers/android

When I log in to an arbitrary veyron_mickey device that has the "arc" label on cautotest, it doesn't look like it's expected to support ARC:

% ssh root@chromeos1-row3-rack9-host2.cros ls -la /opt/google/containers
Password: 
ls: cannot access '/opt/google/containers': No such file or directory

Does the arc label need to be removed from these devices, similar to issue 813441?

Comment 1 by bhthompson@google.com, Mar 16 2018 

veyron_mickey should not have the arc label, it sounds like this is a labeling bug. 

This is stranger than the clapper bug, as there should never have been a condition where veyron_mickey had an arc label previously, if the label setting code in the provisioning step is broken it might keep coming back.

Comment 2 by ihf@chromium.org, Mar 16 2018

Cc: -ihf@chromium.org
¯\_(ツ)_/¯

Comment 3 by dgarr...@chromium.org, Mar 16 2018 

It could also have been applied manually somehow.

If it's a single board and doesn't recur, that's the most likely explanation.

Comment 4 by derat@chromium.org, Mar 20 2018 

Bernie and Don, who's the right person to look into this?

Comment 5 by dgarr...@chromium.org, Mar 20 2018

Owner: jrbarnette@chromium.org
The current deputy is a good choice.

Comment 6 by jrbarnette@chromium.org, Mar 20 2018

Status: Started (was: Untriaged)

Comment 7 by jrbarnette@chromium.org, Mar 20 2018 

$ atest label remove -m $M arc
Removed from label 'arc' hosts: 
	chromeos1-row3-rack9-host2, chromeos1-row4-rack9-host2,
	chromeos15-row1-rack11-host2, chromeos15-row1-rack8-host2,
	chromeos4-row3-rack10-host1, chromeos4-row3-rack10-host10,
	chromeos4-row3-rack10-host12, chromeos4-row3-rack10-host13,
	chromeos4-row3-rack10-host14, chromeos4-row3-rack10-host15,
	chromeos4-row3-rack10-host17, chromeos4-row3-rack10-host18,
	chromeos4-row3-rack10-host19, chromeos4-row3-rack10-host2,
	chromeos4-row3-rack10-host20, chromeos4-row3-rack10-host3,
	chromeos4-row3-rack10-host4, chromeos4-row3-rack10-host5,
	chromeos4-row3-rack10-host6, chromeos4-row3-rack10-host7,
	chromeos4-row3-rack10-host8, chromeos4-row3-rack10-host9,
	chromeos4-row3-rack11-host1, chromeos4-row3-rack11-host10,
	chromeos4-row3-rack11-host2, chromeos4-row3-rack11-host3,
	chromeos4-row3-rack11-host4, chromeos4-row3-rack11-host5,
	chromeos4-row3-rack11-host6, chromeos4-row3-rack11-host7,
	chromeos4-row3-rack11-host8, chromeos4-row3-rack11-host9

Comment 8 by jrbarnette@chromium.org, Mar 20 2018

Status: Fixed (was: Started)
►

Sign in to add a comment