touch /var/tmp/provision_failed should be the first action in provision flow |
||||||||
Issue descriptionWe have some forms of provision failure that are not triggering appropriate repair actions, because the failure occurs before touching the /var/tmp/provision_failed file. (for instance, looking at the log, it seems like we copy stateful payload and try to run the devserver on DUT before we touch this file; failures in those steps due to bad state on the DUT will not get properly repaired) We should move this to be the vert first action performed in the autoupdate.
,
Oct 6 2016
The relevant code seems to be in src/platform/dev/cros_update.py:184
,
Oct 7 2016
The following revision refers to this bug: https://chromium.googlesource.com/chromiumos/platform/dev-util/+/fdfd1e37ae81f0283ecfaabcb738a54c5d5b0c68 commit fdfd1e37ae81f0283ecfaabcb738a54c5d5b0c68 Author: xixuan <xixuan@chromium.org> Date: Thu Oct 06 21:55:17 2016 Devserver: make touch provision_failed as the first action in provision This CL make 'touch /var/tmp/provision_failed' as the first action in CrOS Auto-Update flow. BUG= chromium:653368 TEST=Run repair in local autotest. Change-Id: I29a47ac4735ad559f1fff5133d1efabe9aa5e435 Reviewed-on: https://chromium-review.googlesource.com/394888 Commit-Ready: Aviv Keshet <akeshet@chromium.org> Tested-by: Aviv Keshet <akeshet@chromium.org> Reviewed-by: Aviv Keshet <akeshet@chromium.org> [modify] https://crrev.com/fdfd1e37ae81f0283ecfaabcb738a54c5d5b0c68/cros_update.py
,
Oct 11 2016
,
Dec 8 2016
,
Mar 4 2017
,
Apr 17 2017
,
May 30 2017
,
Aug 1 2017
,
Oct 14 2017
|
||||||||
►
Sign in to add a comment |
||||||||
Comment 1 by akes...@chromium.org
, Oct 6 2016