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

Issue 600525 link

Starred by 1 user
Status: WontFix
Owner:
█ kevcheng@chromium.org
Last visit > 30 days ago
Closed: Apr 2016
Cc:
█ jrbarnette@chromium.org
█ krisr@chromium.org
█ kevcheng@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 3
Type: Bug



Sign in to add a comment

some cros devices have invalid hwids

Project Member Reported by kevcheng@chromium.org, Apr 4 2016 
hwid generated labels will be broken for certain devices with invalid hwids.  Is that ok?

example device:
- lulu (chromeos1-row2-rack1-host3)
# crossystem hwid
LULU TEST A-A 7705

- samus (chromeos1-row1-rack1-host2)
# crossystem hwid
SAMUS TEST 8028


When I try to use these hwids, I get back:
"error": "(u'HWID not found SAMUS TEST 8028', HWIDException(\"HWID string u'SAMUS TEST 8028' is neither base32 nor base8192 encoded\",))",
 "kind": "chromeoshwid#resourcesItem",

Are these devices out of luck? Or should their funky hwid also get recognized?

Comment 1 by jrbarnette@chromium.org, Apr 4 2016

Cc: krisr@chromium.org
These devices are probably running pre-production hardware.

There's a case that they should be removed from the lab.  If
we can't remove them, the owners will have to rewrite the HWID
to have some valid value.

I don't think it's in our interest to work around this in
source code.

Comment 2 by haddowk@chromium.org, Apr 6 2016

Owner: kevcheng@chromium.org
Removing myself as the owner, I agree that devices in the lab where the HWID can not decode should either be decommissioned or if there is simply not enough stock of replacement devices we will have to correct the HWID.   There might be some exceptions made for very old HWID (v2 v1 ? ) like ALEX but lets discuss that case in a separate bug.

Comment 3 by kevcheng@chromium.org, Apr 22 2016

Status: WontFix (was: Untriaged)
Sounds like we'll do this on a case-by-case basis.

Comment 4 by benhenry@google.com, Apr 27 2016

Components: Infra>Client>ChromeOS
Labels: -Infra-ChromeOS
►

Sign in to add a comment