Blacklist versions as part of Rollback along with unittests.
This CL adds version blacklisting as part of AU Rollback. A few additional
things:
1) Since this pref must persist across rollback I have introduced a
powerwash_safe_prefs as part of system_state that will persist across
powerwashes.
2) Fixed bug where we needed to read the device policy (which is read during an
update_check before Rollback would work).
3) Some refactoring to move pref constants to constants.
4) Passing keepimg into our powerwash command so we don't wipe the old
partitions.
BUG=chromium:252589 chromium:254217
TEST=Unittests + test on device + using rollback with and without powerwash
checking preserve state.
Change-Id: I991fad944594944425fd9941e10b30a919f2b83b
Reviewed-on: https://gerrit.chromium.org/gerrit/59518
Reviewed-by: Chris Sosa <sosa@chromium.org>
Tested-by: Chris Sosa <sosa@chromium.org>
Commit-Queue: Chris Sosa <sosa@chromium.org>
diff --git a/omaha_request_action.cc b/omaha_request_action.cc
index 6a6f87a..2c45c7d 100644
--- a/omaha_request_action.cc
+++ b/omaha_request_action.cc
@@ -636,7 +636,7 @@
// Set the version.
output_object->version = XmlGetProperty(manifest_node, kTagVersion);
if (output_object->version.empty()) {
- LOG(ERROR) << "Omaha Response has manifest version";
+ LOG(ERROR) << "Omaha Response does not have version in manifest!";
completer->set_code(kErrorCodeOmahaResponseInvalid);
return false;
}