update_engine: Report VPD write failure to UMA Currently we see many first actives to come from non-FSI images. But we have not been able to figure out why. This CL, reports a new error kFirstActiveOmahaPingSentPersistenceError when writing the first active omaha flag into VPD fails. This allows us to see if that is the actual cause of the problem. CL:1062659 adds the enum value on the Chrome side. BUG=chromium:833980 TEST=unittests TEST=precq Change-Id: I65e233c5f895489ba905494fb20d7b00d0c4af10 Reviewed-on: https://chromium-review.googlesource.com/1062662 Commit-Ready: ChromeOS CL Exonerator Bot <[email protected]> Tested-by: Amin Hassani <[email protected]> Reviewed-by: Amin Hassani <[email protected]> Reviewed-by: Ben Chan <[email protected]>
diff --git a/common/error_code.h b/common/error_code.h index c301155..a7fee2a 100644 --- a/common/error_code.h +++ b/common/error_code.h
@@ -78,6 +78,7 @@ kUpdatedButNotActive = 52, kNoUpdate = 53, kRollbackNotPossible = 54, + kFirstActiveOmahaPingSentPersistenceError = 55, // VERY IMPORTANT! When adding new error codes: //