Partner is missing .boto file within chroot

[Niko Tsirakis]

Hi folks,

I am working with one of our partners to build ChromeOS locally. While our team's boards are private, we are attempting to build the public parent (fizz). Out of the box, this resulted in 401 errors when attempting to access some GS buckets:

WARNING: GS_ERROR: b"ServiceException: 401 Anonymous caller does not have storage.objects.get access to the Google Cloud Storage object. Permission 'storage.objects.get' denied on resource (or it may not exist).\n" Not logged in. See https://www.chromium.org/chromium-os/developer-library/reference/tools/gsutil/#configure-authentication-boto for instructions.

The partner has already configured their auth in their host environment by running commands in the link from the error message, and the host .boto file exists. What I'm not seeing is a .boto file inside the chroot, which I assume is needed to access these resources. Can someone please assist? Thanks,

-Niko

[Mike Frysinger]

partners should not be running `gsutil` directly inside the SDK.  what command exactly are they trying to run ?  `cros build-packages` or `emerge-$BOARD` should work fine.

this was announced earlier this year:
https://groups.google.com/a/chromium.org/g/chromium-os-dev/c/PUC1IRD6wlQ/m/cKrQiDziAwAJ
-mike

--
--
ChromiumOS Developers mailing list: chromiu...@chromium.org
View archives, change email options, or unsubscribe:
https://groups.google.com/a/chromium.org/group/chromium-os-dev

[Niko Tsirakis]

`cros build-packages` is what's failing. Thanks for the link - are the paths to the per-overlay boto files hardcoded then? ie is it expected that `~/.boto` does not exist in chroot?

In case it helps, here are the failing packages for one of the runs:
Failed Packages: x11-libs/libdrm-2.4.124 sys-libs/libnvme-1.6
And here is the full error log provided by the partner: https://docs.google.com/document/d/1NXiLDg_rhINIpv1QrWSx78lYo9g7OOBEt1JnZfRM4tU/edit?tab=t.0 

[Mike Frysinger]

mesa failing to build is most likely not due to the boto/binpkg errors.  those are an optimization, and if it fails, they're skipped.  if they were fatal, the build would have aborted, but it didn't.

the log also indicates they don't actually have the private fizz overlay in their checkout, so they're only building the public fizz board.  you should work with them to resolve that.

-mike

[Niko Tsirakis]

Thanks for the help Mike. That sounds promising.

[Kyle Williams]

Is the private fizz overlay required to build for fizz.
They are only attempting to test a library they are developing on a CN65 Teemo.
The command they have used that is failing is `cros build-packages --board=fizz`

Kyle Williams | Software Engineer kdg...@google.com | Core Devices, Meeting Solutions 111 8th Avenue, New York, NY 10011

[Mike Frysinger]

only eng/SIE can really say whether the public fizz build works

that said, they seem to have some private overlays mixed in as I'm pretty sure they're including chromeos-partner-overlay. if they want a public build, they shouldn't include any internal repos like that. 

-mike