Link to the build logs : https://uberchromegw.corp.google.com/i/chromeos/builders/coral-paladin

and one of the build packages error logs:
https://logs.chromium.org/v/?s=chromeos%2Fbb%2Fchromeos%2Fcoral-paladin%2F3503%2F%2B%2Frecipes%2Fsteps%2FBuildPackages%2F0%2Fstdout

 Issue 850142  has been merged into this issue.

Good info on GS bucket status in duped bug.

someone with admin access to CPFE/BCS is required to resolve this.  i don't have that access.

if someone has access, they could fix this with the gsutil command:
gsutil cp gs://chromeos-binaries/HOME/bcs-coral-private/overlay-coral-private/chromeos-base/chromeos-firmware-coral/Coral_EC.10068.63.0.tbz2#1528102771464385 gs://chromeos-binaries/HOME/bcs-coral-private/overlay-coral-private/chromeos-base/chromeos-firmware-coral/Coral_EC.10068.63.0.tbz2

we might be able to mitigate it in the mean time by signing into the CQ bot that's failing and manually cache the archive in the distdir:
gsutil cp gs://chromeos-binaries/HOME/bcs-coral-private/overlay-coral-private/chromeos-base/chromeos-firmware-coral/Coral_EC.10068.63.0.tbz2#1528102771464385 .../chromiumos/.cache/distfiles/target/

bhthompson: Do you have access?

Thanks Mike, I ran the command to restore the older version, and will instruct partner (who overwritten the file) to do it the right way.

Keeping the bug open until coral-paladin completes successfully.

My local coral build looks all right -- started coral-paladin to see if the problem is resolved.

coral-paladin looks OK now. Marking the bug fixed.
Thanks.