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

Issue 796682 link

Starred by 1 user

Issue metadata

Status: Untriaged
Owner: ----
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: ----



Sign in to add a comment

lakitu-st-release signing failed

Project Member Reported by sheriff-...@appspot.gserviceaccount.com, Dec 20 2017

Issue description

Filed by sheriff-o-matic@appspot.gserviceaccount.com on behalf of bmgordon@google.com

lakitu-st-release:557 failed

This is the error text:
03:58:20: INFO: Received results for: ChromeOS-base-R65-10232.0.0-lakitu-st.instructions.json
03:58:20: INFO: {
    "status": {
        "status": "failed", 
        "summary": "section lakitu-st-mp for keyset lakitu-st-mp: channel=dev (must be channel=stable)", 
        "details": "Traceback (most recent call last):\n  File \"//cros/signer/signing_poller.py\", line 905, in SignArtifacts\n    (work_dir, insn_cfg) = self.GetRemoteArtifact(insn, metadata)\n  File \"//cros/signer/signing_poller.py\", line 591, in GetRemoteArtifact\n    insn_cfg = self._ValidateInstructions(insn, local_insn_path)\n  File \"//cros/signer/signing_poller.py\", line 314, in _ValidateInstructions\n    instruction, expected_value))\nInstructionError: section lakitu-st-mp for keyset lakitu-st-mp: channel=dev (must be channel=stable)\n", 
        "current-time": "Wed, 20 Dec 2017 11:57:55 +0000 (UTC)"
    }, 
    "time": {
        "start": "Wed, 20 Dec 2017 11:57:51 +0000 (UTC)"
    }, 
    "metadata-version": "1", 
    "bot-hostname": "chromeos-signing33.ams.corp.google.com"
}

Builders failed on: 
- lakitu-st-release: 
  https://luci-milo.appspot.com/buildbot/chromeos/lakitu-st-release/557


 
Cc: martinroth@chromium.org jrbarnette@chromium.org
Components: Infra>Client>ChromeOS
Project Member

Comment 3 by sheriffbot@chromium.org, Dec 21

Labels: Hotlist-Recharge-Cold
Status: Untriaged (was: Available)
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Sign in to add a comment