New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 894814 link

Starred by 1 user
Status: Verified
Owner:
█ hunyadym@chromium.org
Last visit > 30 days ago
Closed: Oct 23
Cc:
vaandres@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug



Sign in to add a comment

Rollback to target version new policy values are not set

Project Member Reported by hunyadym@chromium.org, Oct 12 
Chrome OS 11105
Chrome 71.0.3565.0

policy_provider_->GetDevicePolicy().GetRollbackToTargetVersion(
          &rollback_to_target_version_int)

Here: http://cs/chromeos_public/src/aosp/system/update_engine/update_manager/real_device_policy_provider.cc?l=135&rcl=1aafbfdc30b20d9d6a193a0b992234db710cf3c5

Returns false if the value is 3 (ROLLBACK_AND_RESTORE_IF_POSSIBLE) or 4 (ROLLBACK_ONLY_IF_RESTORE_POSSIBLE).

Comment 1 by hunyadym@chromium.org, Oct 12 

Reason is probably that protofiles was uprev'd at 70.0.3535 for the last time, and the CL landed in 70.0.3538.0.

Comment 2 by hunyadym@chromium.org, Oct 23 

This should be fixed from 72.0.3582 per crbug.com/895457

Comment 3 by hunyadym@chromium.org, Oct 23

Status: Fixed (was: Assigned)

Comment 4 by vaandres@google.com, Jan 10

Status: Verified (was: Fixed)
verified proper values are set for RollbackToTargetVersion =3 and 4
►

Sign in to add a comment