Issue metadata
Sign in to add a comment
|
Rollback filed on M66 |
||||||||||||||||||||
Issue descriptionPlease specify Cr-* of the system to which this bug/feature applies (add the label below). Steps To Reproduce: (1) AU from M65 to M66 TOT (2) Perform rollback from crosh> (3) Expected Result: Should rollback to M65 version. Actual Result: Rollback Failed. How frequently does this problem reproduce? (Always, sometimes, hard to reproduce?) What is the impact to the user, and is there a workaround? If so, what is it? Please provide any additional information below. Attach a screen shot or log if possible. For graphics-related bugs, please copy/paste the contents of the about:gpu page at the end of this report. Log Info *********************************************************************** [0206/113504:INFO:update_attempter.cc(738)] UpdateAttempter::GetRollbackSlot [0206/113504:INFO:update_attempter.cc(743)] Installed slots: 2 [0206/113504:INFO:update_attempter.cc(744)] Booted from slot: A [0206/113504:INFO:update_attempter.cc(761)] No other bootable slot found. [0206/113504:ERROR:common_service.cc(93)] AttemptRollback(...): Domain=update_engine, Code=org.chromium.UpdateEngine.Error.Failed, Message=Rollback attempt failed. [0206/113504:ERROR:common_service.cc(57)] Sending Update Engine Failure: AttemptRollback@../../../../../../../tmp/portage/chromeos-base/update_engine-0.0.3-r3137/work/update_engine-0.0.3/aosp/system/update_engine/common_service.cc:93: Rollback attempt failed.
,
Mar 9 2018
Not reproduced after one more N+1 update. I will post more info if i can repro it again. |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by ahass...@chromium.org
, Mar 9 2018