The WritableVerifier should test both stateful and encrypted stateful
Reported by
jrbarnette@chromium.org,
Jun 20 2016
|
|||||
Issue descriptionRecently, we had a failure (see bug 618744) where encrypted stateful on a DUT went read-only, but the unencrypted stateful was fine. The result was a DUT that couldn't Provision (it couldn't create a file in /var/tmp), but Verify (and therefore Repair) passed without error (because it only tests unencrypted). We need the WritableVerifier class to test both stateful and encrypted stateful for trouble.
,
Jun 20 2016
,
Jun 20 2016
,
Jun 21 2016
The following revision refers to this bug: https://chromium.googlesource.com/chromiumos/third_party/autotest/+/781851b6fbbe095ae3cec935d7f61289863afc7b commit 781851b6fbbe095ae3cec935d7f61289863afc7b Author: Richard Barnette <jrbarnette@chromium.org> Date: Mon Jun 20 17:13:13 2016 [autotest] In verify, test for readonly encrypted stateful. It's possible for encrypted stateful (meaning, mostly, /var) to go read-only while the regular, unencrypted stateful partition is just fine. This enhances the WritableVerifier to test both encrypted and unencrypted stateful. BUG= chromium:621557 TEST=Run Repair in a local Autotest instance Change-Id: Ia87565fb1ca96c701a1e097edf8d8f9f28805c23 Reviewed-on: https://chromium-review.googlesource.com/354082 Commit-Ready: Richard Barnette <jrbarnette@chromium.org> Tested-by: Richard Barnette <jrbarnette@chromium.org> Reviewed-by: Aviv Keshet <akeshet@chromium.org> [modify] https://crrev.com/781851b6fbbe095ae3cec935d7f61289863afc7b/server/hosts/cros_repair.py
,
Jun 21 2016
,
Jul 12 2016
,
Aug 12 2016
Closing. please reopen if its not fixed. |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by akes...@chromium.org
, Jun 20 2016Labels: dut-health
Owner: jrbarnette@chromium.org
Status: Assigned (was: Available)