Issue metadata
Sign in to add a comment
|
Quick provision error status should report both errors |
||||||||||||||||||||
Issue descriptionWhen quick provisioning fails, it falls back to the legacy path, and then if that fails, the final failing exception is written into the auto-update status which can be queried by the client through the get_au_status RPC. Information from the quick provisioning attempt should be included in the failure including: - the final status at the time of quick provision failing - the results of the ssh failure message This will make it easier to debug provision attempts when using a load generator without having direct access to the devserver (which is already somewhat difficult to parse due to the sheer number of devices that might be provisioning at the same time) since the logs could directly be retrieved and stored on the client.
,
May 30 2018
My work on provisioning code paths is ready to start incorporating quick-provisioning related flows, as soon as I resume work on it after my deputy shift.
,
Jun 4 2018
The NextAction date has arrived: 2018-06-04
,
Jun 22 2018
Rollout of the new provisioning code has started. The feature will be rolled out to all servers next Monday, 6/22. After that, we should look at the current logging, and evaluate what this request means in terms of the new code.
,
Jun 25 2018
The NextAction date has arrived: 2018-06-25
,
Jun 26 2018
> Rollout of the new provisioning code has started. The feature will be
> rolled out to all servers next Monday, 6/22.
<sigh> This rollout has been delayed. We're waiting for this CL to get
in to the tree and then be pushed to prod:
https://chromium-review.googlesource.com/c/chromiumos/third_party/autotest/+/1114332
Once we're satisfied with metrics tracking for the new code, we'll resume
rollout.
,
Sep 11
I think that this is probably not relevant in the context of the current provisioning code. Passing back to davidriley@ to describe what this means in terms of the current code, or else just close as WontFix. |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by akes...@chromium.org
, May 30 2018Owner: jrbarnette@chromium.org
Status: Assigned (was: Untriaged)