+Ketaki for 57

Are these actually available now?

This should happen naturally as part of R57 stable promotion which is beginning this week.

Recovery image is there, you can find it if you type full HWID (e.g. KEFKA D25-A3H-O25-A2E-Q5X)
Alternatively, you can also select by  Model list and find it there

ps. Note that this is because some devices are enforced to use a HWID pattern so you need to keep entering characters until the match is found

For KEFKA the match is "^KEFKA \w{3}-A\w{2}(-\w{3})*" hence if you only type KEFKA the match is not yet made yet.. 

Basically above match is making sure that second 3 digit group starts with an A (e.g. KEFKA D25-A3H-O25-A2E-Q5X)

+stevenh@ since he will have more context about limiting to only this match 

For KEFKA (Clamshell),   the match is "^KEFKA \w{3}-A\w{2}(-\w{3})*"
For SABIN (Convertible), the match is "^KEFKA \w{3}-B\w{2}(-\w{3})*"

I believe the recovery tool response is a byproduct of Zerg implementations using same image, but unique implementation features delineated in the HWID.

It seems like the recovery tool should operate at the 'device' level when showing actual marketing names, but at the 'board' level when HWID is being entered?

We should not generally require separate recovery images for systems that share the same board name in the HWID, we have only one historical incident of this on alex/zgb due to a modem software licensing problem, so this is probably safe to say if the characters before a space in the HWID match there is only one image.

+GE folks

I am not sure what the HWID regex field is used for other than this aspect of the recovery tool?

If it does nothing else, it might be fine to just change the regex to "^KEFKA .*" then the tool would give an image after just typing in KEFKA. 

We can also say this is working as intended and leave it as it is, I think most users don't necessarily have an expectation that they should be pointed to a recovery image after typing in just a portion of the HWID.

This is WAI.  This is used in the zerg/whitelabel case so that as users type the HWID, they will be able to see their device's marketing name when they are performing the recovery.

Ah ok, so even though we should be able to know what image they would need, it is more consistent for the user for the UI to show the proper marketing name. 

Seems reasonable, thanks for the clarification.

This clarifies the confusion with the images in the Recovery Tool, but Dell Chromebook 11 (3180) devices are not reporting the Model to the Admin Console. Is there an update on that problem?

Hi team,

I'm reopening this bug since even if the image has been added in the tool, the 'Model' field in the Admin Console is not being populated.

Steps to reproduce 
1. Enroll a Dell Chromebook 11 (3180). 
2. Make sure the device is updated and syncing to the servers. 
3. Navigate to ‘Device management > Chrome devices’. 
4. Look for the device serial number, and click on it. 
5. Expand ‘Hardware and OS’, and the ‘Model’ field will be empty. 

Any ideas if there's something in the back-end that's missing for this particular device?.

To rule out misconfiguration we have verified:

* 'Device state reporting' policy is enabled for the org unit where the device is.
* No network issues. Tried in a completely open network.
* Other devices (different model) in the same org unit, and same network report the model.
* Neither of the DELL Chromebook 11 (3180) devices report the model.

Thanks!

Passing to Steven to evaluate missing model in admin console 

+ mdrasner

VPD settings, launch date and configurations on the hardware management side look correct.

Matt, is there an additional setting on Admin Control side that needs to be configured for model name to be displayed correctly?  Where is the model name info held for Admin Console?  Thanks.

This likely has to do with a change to which file we reference to report the model information (discussed further in the email thread) and not sure if that was completed, but our team will investigate and look to confirm.

It's important to note that /googledata/download/chromeos/recovery/onhub_recovery.json has not been updated since 10/26/2016 and you should move to the live version at https://dl.google.com/dl/chromeos/recovery/recovery.json if you haven't done it yet. We added a new tool that skips the processing of checking the changes in Perforce.

Yes that was a task that was missed from end of last year. dkalin@ will be working on that update via b/36686985.

We can close this instance and folks can follow along there if interested.

Thanks a lot, we'll follow the progress in b/36686985

Closing this issue as Fixed.  Reopen if progress on b/36686985 does not resolve the problem.

May I re-open this? Originally and per #10 there were 2 questions here for kefka:
1. Model not found when using recovery json -- fixed.
2. Model field is empty in CPanel -- not fixed.
b/36686985 is just about using proper recovery json file.

Reporduced in QD5:
(1) Enroll kefka Dell Chromebook 11 (3180).
(2) Check device details in CPanel.
(3) Note that "Model" is not populated for the device.

It's very interesting to know per #13
Where is the model name info held for Admin Console? And how can we fix that?
Steven, may I assign this to you please?

Reassigning to Matt for now. If not the appropriate place, feel free to assign back to me.

I'd like to add that apparently what's causing this problem may trigger other models to report wrong model. For instance:

We've received reports that Asus Chromebook C301SA are reporting as if they are Asus Chromebook C202SA (a total amount of 150 devices affected). Other report we've received is from the Lenovo N23 reporting as N22

See VPD info extracted from a C301SA:

customization_id=ASUS-TERRA3 
initial_locale=en-US 
initial-timezone=America/Los_Angeles 
keyboard_layout=xkb:us::eng 
region=US 
rlz_brand_code_ASUK 
ActivateDate=2016-35 

See VPD info extracted from the Lenovo N23:

"model_name"="Lenovo N23 Chromebook"
"region"="us" "rlz_brand_code"="LEAL"
"customization_id"="LENOVO-REKS3"
"ActivateDate"="2017-13"

Can you please take a look at this as well?. I suspect that what causes the Dell Chromebook 11 (3180) to not report the model may trigger these models to send wrong info.

This is fixed now, Kefka and other recent boards should now be showing in both recovery tool and admin console with proper model name.

If there are other boards which do not display a model name or display an incorrect model name please open a new bug in the proper location (recovery tool > crbug, admin console > internal bug)