User left in a non-recoverable state if profile removal after failed migration fails. |
|||||||
Issue descriptionIf the crypto migration fails and the subsequent profile removal also fails (this can happen if the file system has corrupt data that can't be removed) the end result is that the user has a (mostly) empty invalid profile, so they can't log in to it nor can they create a new one. The only solutions are to somehow fix the corruption (not sure this is possible in many cases) or format the stateful partition. Its possible that other accounts on the device can still be used normally, so I don't think that just immediately wiping the stateful partition is the right way forward. Assigning to Hiro to figure out what the UX should be for this scenario. For reference looking at last 28 days of beta devices we see this case in ~.04% of migrations.
,
Jul 11 2017
bartfab@: Do you remember if the device was rebooted between the migration failure and when you tried removing the profile via right-click?
,
Jul 11 2017
After migration had failed, I got a dialog with two buttons, "Report an issue" and "Restart." I hit one, then the other. The device rebooted at that point. I did try logging in several times before attempting to remove the profile. I did not reboot again between these tries - the failed login attempts might have left something half-mounted.
,
Jul 11 2017
What's the probability and duration if we try to fix the corruption? UX would depend on these points.
,
Jul 11 2017
Probability of corruption (rough estimate based on 28 days of beta traffic) is .04%. Not sure about fixing it, gwendal had some comments on the matter over chat so assigning to him for input.
,
Jul 12 2017
,
Dec 27 2017
,
Aug 10
|
|||||||
►
Sign in to add a comment |
|||||||
Comment 1 by hashimoto@chromium.org
, Jul 11 2017