FYI, also tried on R71-11055.0.0, still reproes. Tests running vs M70 pass enrollment so it's seems like a client regression.

After some investigation I found the cause: https://crrev.com/978c0e67732f7829611e050602dea4e714225ee8.

It turns out that this has been reverted 3 days ago in https://crbug.com/854101#c11. The commit was only on master for a day before being reverted so it was very quickly fixed!

However, we're stuck with the broken version until CrOS picks up a new snapshot of Chrome.

Re-opening this issue as CrOS have not picked up a new Chrome version for a while. I believe all enrollment of CrOS devices to be broken.

Assigning to asavery@ who is sheriff for CrOS according to goldeneye.

I'm the M71 TPM; I've been pinging re: the Chrome PFQ being down for M71.   Hoping to get that resolved.   This should go to the gardner, btw.

Also, could this be a DUP of crbug/883376?  Thx

It looks like 883376 is the same issue, yes, though this one predates the other one :)

When will CrOS pick up a new version of Chrome as the issue is already fixed there (see comment #4).

Yes,  https://crbug.com/883376  looks like a dupe of this bug.

Thanks for the comment in #9; I'll make the other bug as a DUP

 Issue 883376  has been merged into this issue.

Assigning to newcomer@ who is the gardener this week, as per comment #8.

Thanks. Not sure what's actionable for me here besides continuing to garden.

According to #4 a new chrome import with the proper fix is needed.

This is now been broken for a full week - what is the proper way to address such regressions in the future?

We just manually uprevved so, maybe this will be fixed in the latest canary.

Yes, enrollment works again (https://screenshot.googleplex.com/DzVmVvo3Try.png). Thanks!