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

Issue 706540 link

Starred by 1 user

Issue metadata

Status: Duplicate
Merged: issue 705247
Owner: ----
Closed: Mar 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 1
Type: Bug



Sign in to add a comment

signing failing: no space left on device

Project Member Reported by gwendal@chromium.org, Mar 29 2017

Issue description

Several board fails the signing phase. (
For instance:
https://uberchromegw.corp.google.com/i/chromeos/builders/caroline-release/builds/531

Looking at errror reported (enclosed), ther error is:

RunCommandError: return code: 1; command: /cros/vboot_reference/scripts/image_signing/sign_official_build.sh recovery /tmp/signer.6_RKjY/recovery_image.bin /tmp/signer.keydir.UpXnpb/cros/keys/Caroline

...
\u001b[1;32mINFO   : Re-signing (platform) /tmp/tmp.tyZBLFkYC0/mnt/system/priv-app/ExternalStorageProvider/ExternalStorageProvider.apk\u001b[0m
\u001b[1;32mINFO   : Start updating sepolicy\u001b[0m
\u001b[1;32mINFO   : Replacing OTA cert\u001b[0m
\u001b[1;32mINFO   : Reapplying file security context\u001b[0m
\u001b[1;32mINFO   : Repacking squashfs image\u001b[0m
Write failed because No space left on device
FATAL ERROR:Failed to write to output filesystem




 
status.txt
8.6 KB View Download
Labels: Hotlist-CrOS-Sheriffing
Mergedinto: 705247
Status: Duplicate (was: Untriaged)

Sign in to add a comment