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

Issue 712542 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner:
Closed: May 2017
Cc:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug



Sign in to add a comment

TATL Paladin: No Google Storage ACL file googlestorage_acl.txt found in tatl overlay.

Project Member Reported by owenlin@chromium.org, Apr 18 2017

Issue description

https://uberchromegw.corp.google.com/i/chromeos/builders/tatl-paladin/builds/0/steps/UploadPrebuilts/logs/stdio

19:22:19: INFO: RunCommand: /b/cbuild/repository/.cache/common/gsutil_4.19.tar.gz/gsutil/gsutil -o 'Boto:num_retries=10' cat gs://chromeos-prebuilt/host/amd64/amd64-host/chroot-2017.04.17.021851/packages/Packages
19:22:20: ERROR: No Google Storage ACL file googlestorage_acl.txt found in tatl overlay.
19:22:20: ERROR: 

 
Status: Started (was: Assigned)
Ah, I didn't realize internal waterfall implies we need a private bucket. I'll work on that.
Cc: pprabhu@chromium.org
Actually, we shouldn't ever need closed source code in here, so I don't see the need for private overlays.

We aren't working with any partners, and there are no firmware bits and no graphics. There's also no need for secrecy on the VM, so we could just put it on the public waterfall.

pprabhu@: Would there be any problems with putting tatl/tael on the public waterfall? I'm concerned mostly about if the internal waterfall would get confused, or if any conflicts would arise with the external waterfall.
Labels: -Hotlist-CrOS-Sheriffing
label update: This is an experimental paladin, so doesn't deserve sheriff's cycles.

Re #2: Yay for staying public.
See amd64-generic-paladin for an example of how an external paladin can be an important paladin as far as the commit queue is concerned.
https://build.chromium.org/p/chromiumos/waterfall?builder=amd64-generic-paladin

This is a supported case (even predates the internal waterfall iirc)

Cc: vapier@chromium.org
The reason all non generic board paladins are on the internal waterfalls instead of external ones is that released images are all ChromeOS images for the hardware we ship, not chormiumos ones.

If your board only needs chromiumos images, external waterfall is the way to go.
+vapier for more history and better memory than mine.
I'll go ahead and make this external then, thanks!

Comment 6 by vapier@chromium.org, Apr 19 2017

yeah, would prefer to do public builds only whenever possible
Project Member

Comment 7 by bugdroid1@chromium.org, Apr 22 2017

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/chromite/+/ab70e1771dea3e5f71c07fd3a5907f50f6c50d60

commit ab70e1771dea3e5f71c07fd3a5907f50f6c50d60
Author: Stephen Barber <smbarber@chromium.org>
Date: Sat Apr 22 04:57:35 2017

Move termina boards to external waterfall

BUG= chromium:712542 
TEST=cbuildbot --local tatl-full

Change-Id: Ifccd436770a1cd0deb2dc0e9bc95a14738083530
Reviewed-on: https://chromium-review.googlesource.com/480985
Commit-Ready: Stephen Barber <smbarber@chromium.org>
Tested-by: Stephen Barber <smbarber@chromium.org>
Reviewed-by: Prathmesh Prabhu <pprabhu@chromium.org>

[modify] https://crrev.com/ab70e1771dea3e5f71c07fd3a5907f50f6c50d60/cbuildbot/config_dump.json
[modify] https://crrev.com/ab70e1771dea3e5f71c07fd3a5907f50f6c50d60/cbuildbot/waterfall_layout_dump.txt
[modify] https://crrev.com/ab70e1771dea3e5f71c07fd3a5907f50f6c50d60/cbuildbot/chromeos_config.py

Status: Fixed (was: Started)
Waterfall restarted, tatl-paladin is green.

Sign in to add a comment