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

Issue 617979 link

Starred by 2 users
Status: Verified
Owner:
█ bhthompson@chromium.org
Last visit > 30 days ago
Closed: Jun 2016
Cc:
josephsih@chromium.org
█ vpalatin@chromium.org
█ sha...@chromium.org
vapier@chromium.org
EstimatedDays: ----
NextAction: ----
OS: Linux , Chrome
Pri: 0
Type: Bug



Sign in to add a comment

many boards signing failing due to unknown rootfs size

Project Member Reported by vapier@chromium.org, Jun 7 2016 
this CL:
https://chromium-review.googlesource.com/350150

broke signing:
https://uberchromegw.corp.google.com/i/chromeos/builders/samus-release/builds/3266/steps/SignerTest/logs/stdio

due to rootfs size unknown:
Kernel dm= parameter does not match any expected values!
Actual:   1 vroot none ro 1,0 3584000 verity payload=PARTUUID=%U/PARTNROFF=1 hashtree=PARTUUID=%U/PARTNROFF=1 hashstart=3584000 alg=sha1 root_hexdigest=0b1e6351f0305785b573810c2a38ac28ad08138b salt=b5022ae598c25eb9f8964a50670212d46fa4ae35b7d991d336733b7dc7a9ad48
Expected: 
Expected (regex): vroot none ro,0 \(1536000\|1740800\|1843200\|2097152\|2506752\|3334144\|3776512\|6291456\) verity %U+1 %U+1 \1 0 sha1 MAGIC_HASH vroot none ro,0 \(1536000\|1740800\|1843200\|2097152\|2506752\|3334144\|3776512\|6291456\) verity payload=%U+1 hashtree=%U+1 hashstart=\1 alg=sha1 root_hexdigest=MAGIC_HASH vroot none ro,0 \(1536000\|1740800\|1843200\|2097152\|2506752\|3334144\|3776512\|6291456\) verity payload=%U+1 hashtree=%U+1 hashstart=\1 alg=sha1 root_hexdigest=MAGIC_HASH salt=MAGIC_SALT 1 vroot none ro 1,0 \(1536000\|1740800\|1843200\|2097152\|2506752\|3334144\|3776512\|6291456\) verity payload=%U+1 hashtree=%U+1 hashstart=\1 alg=sha1 root_hexdigest=MAGIC_HASH salt=MAGIC_SALT 2 vboot none ro 1,0 \(1768000\|2129920\|2545920\) bootcache %U+1 \1 MAGIC_HASH [0-9]\+ [0-9]\+ [0-9]\+, vroot none ro 1,0 \(1536000\|1740800\|1843200\|2097152\|2506752\|3334144\|3776512\|6291456\) verity payload=254:0 hashtree=254:0 hashstart=\2 alg=sha1 root_hexdigest=MAGIC_HASH salt=MAGIC_SALT 1 vroot none ro 1,0 \(1536000\|1740800\|1843200\|2097152\|2506752\|3334144\|3776512\|6291456\) verity payload=PARTUUID=%U/PARTNROFF=1 hashtree=PARTUUID=%U/PARTNROFF=1 hashstart=\1 alg=sha1 root_hexdigest=MAGIC_HASH salt=MAGIC_SALT 2 vboot none ro 1,0 \(1768000\|2129920\|2545920\) bootcache PARTUUID=%U/PARTNROFF=1 \1 MAGIC_HASH [0-9]\+ [0-9]\+ [0-9]\+, vroot none ro 1,0 \(1536000\|1740800\|1843200\|2097152\|2506752\|3334144\|3776512\|6291456\) verity payload=254:0 hashtree=254:0 hashstart=\2 alg=sha1 root_hexdigest=MAGIC_HASH salt=MAGIC_SALT

Comment 1 by vapier@chromium.org, Jun 7 2016

Cc: vpalatin@chromium.org josephsih@chromium.org sha...@chromium.org
Labels: Build-Official-Signing
Summary: many boards signing failing due to unknown rootfs size (was: samus signing failing due to unknown rootfs size)
hmm, not 100% sure it's that CL ... a bunch of other boards are broken in the same way

https://uberchromegw.corp.google.com/i/chromeos/builders/terra-release/builds/98/steps/SignerTest/logs/stdio
https://uberchromegw.corp.google.com/i/chromeos/builders/ultima-release/builds/96/steps/SignerTest/logs/stdio

samus/terra/ultima/reks/cyan/celes/edgar/strago/umaro at least

Comment 2 by sha...@chromium.org, Jun 7 2016 

https://chromium-review.googlesource.com/#/c/350114/ might be the cause for the other boards. I'm going to speculatively revert both CLs.

Comment 3 by sha...@chromium.org, Jun 7 2016 

Oh wait, that CL hasn't even landed yet.

Comment 4 by sha...@chromium.org, Jun 7 2016 

https://chromium-review.googlesource.com/#/c/345990/ (braswell) has landed though. Reverting...
Project Member

Comment 7 by bugdroid1@chromium.org, Jun 7 2016 

The following revision refers to this bug:
  https://chrome-internal.googlesource.com/chromeos/cros-signing/+/9b6eaf0b07d28703fa98779993a73cf72a2f0d57

commit 9b6eaf0b07d28703fa98779993a73cf72a2f0d57
Author: Bernie Thompson <bhthompson@google.com>
Date: Tue Jun 07 16:19:39 2016

Comment 8 by bhthompson@chromium.org, Jun 21 2016

Status: Fixed (was: Assigned)

Comment 9 by abod...@chromium.org, Aug 3 2017

Status: Verified (was: Fixed)
Closing. Please reopen it if its not fixed. Thanks!
►

Sign in to add a comment