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

Issue 620512 link

Starred by 1 user
Status: WontFix
Owner: ----
Closed: Sep 2016
Cc:
█ gkihumba@chromium.org
█ bmahadev@chromium.org
kathrelk...@chromium.org
█ patricia@chromium.org
dchan@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug



Sign in to add a comment

52 branch: Setzer missing builds

Project Member Reported by ka...@chromium.org, Jun 15 2016 
@@@STEP_LOG_LINE@reason@Step('cbuildbot [setzer-release]') failed with return_code 1@@@

Golden eye URL: https://cros-goldeneye.corp.google.com/console/listBuild?boards=setzer
Screenshot: https://screenshot.googleplex.com/mkzq6CVx3Es

Comment 1 by kathrelk...@chromium.org, Jun 16 2016 

Setzer M51 and M53 builds are now signed mp, but our last M52 image (8350.13.0, from 5-30) is signed premp.  We cannot load even old M52 builds without extra steps to deal with the key difference.  Switching to dev channel from beta or stable leads to an update failure.

Comment 2 by vapier@chromium.org, Sep 30 2016

Owner: ----
Status: WontFix (was: Untriaged)
key selection in releases isn't something the infra team.  that's up to the TPMs/peng.  check out crostools/signer_instructions/ in ToT & in branches.

assuming this isn't really an issue anymore since we've moved past M52.
►

Sign in to add a comment