Authentication fails when building custom Chromium on Chrome OS

[nat...@lenovo-chrome.com]

I needed to make some browser changes for a Chromium OS build I'm working on. I followed the instructions on the developer guide (starting my cros chroot pointing to the browser sources and then doing cros_workon start of the chromeos-chrome package), and successfully built the browser. However, when I try to log in on OOBE using any account I get a "something went wrong" message.

I reverted my Chromium changes and still see the same behavior when building an unmodified browser.

However, when I do cros_workon stop chromeos-chrome to pull in the binary package, authentication works fine. It's only when I'm building my own browser that it fails.

I tried syncing after a week or so just to see if I pulled in some bad bits, but I still see the problem.

Any help would be appreciated!

[Mike Frysinger]

i would start with the base image that's working and then use the Simple Chrome workflow to validate things:

  https://chromium.googlesource.com/chromiumos/docs/+/master/simple_chrome_workflow.md

only once you're confident in the results would you shift back to building an image (or maybe not do that at all depending on what you're trying to do).

-mike

--
--
Chromium Developers mailing list: chromi...@chromium.org
View archives, change email options, or unsubscribe:
http://groups.google.com/a/chromium.org/group/chromium-dev
---
You received this message because you are subscribed to the Google Groups "Chromium-dev" group.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/chromium-dev/93df7592-c050-4c52-a706-8867a2c61894%40chromium.org.

[Nathan Baker]

Thanks for the suggestion. That's definitely a viable debugging step I haven't tried. At some point I am going to need the ability to build an image with all this functionality included out of the box, but perhaps building with a prepackaged chrome would provide additional helpful debugging info.

In the meantime, I'd definitely appreciate help from anyone who knows what might be going on with the login failure!

[nat...@lenovo-chrome.com]

I'm having trouble following those instructions because I can't start the chrome SDK.

[nathan@nathanb-build ~/chromium/src] cros chrome-sdk --board=ultima --nogoma

14:46:58: WARNING: GS_ERROR: AccessDeniedException: 403 nat...@lenovo-chrome.com does not have storage.objects.list access to bucket chromeos-image-archive.

 

14:46:58: ERROR: cros chrome-sdk failed before completing.

14:46:58: ERROR: return code: 1; command: /home/nathan/chromium/.cros_cache/common/gsutil_4.19.tar.gz/gsutil/gsutil -o 'Boto:num_retries=10' cat gs://chromeos-image-archive/ultima-release/LATEST-9916.0.0

AccessDeniedException: 403 nat...@lenovo-chrome.com does not have storage.objects.list access to bucket chromeos-image-archive.

cmd=['/home/nathan/chromium/.cros_cache/common/gsutil_4.19.tar.gz/gsutil/gsutil', '-o', 'Boto:num_retries=10', 'cat', u'gs://chromeos-image-archive/ultima-release/LATEST-9916.0.0'], extra env={'BOTO_CONFIG': '/home/nathan/.boto'}

Is this a workflow that external contributors are able to use?

[Mike Frysinger]

normally you'd use amd64-generic as a public board

-mike

[nat...@lenovo-chrome.com]

Well, I'm building an ultima image for an ultima device in the cros_sdk. I'm assuming mixing and matching is not a best practice.

Is this back to the drawing board? I'm assuming that this sort of authentication failure is not the expected behavior. Figuring out what's going on here would be ideal.

[Ilja Friedel]

Did you setup API keys?

https://chromium.googlesource.com/chromiumos/docs/+/master/simple_chrome_workflow.md#Get-Google-API-keys

On Tue, Sep 19, 2017 at 12:03 PM, <nat...@lenovo-chrome.com> wrote:

Well, I'm building an ultima image for an ultima device in the cros_sdk. I'm assuming mixing and matching is not a best practice.

Is this back to the drawing board? I'm assuming that this sort of authentication failure is not the expected behavior. Figuring out what's going on here would be ideal.

--

--
Chromium Developers mailing list: chromi...@chromium.org
View archives, change email options, or unsubscribe:
http://groups.google.com/a/chromium.org/group/chromium-dev
---
You received this message because you are subscribed to the Google Groups "Chromium-dev" group.

To unsubscribe from this group and stop receiving emails from it, send an email to chromium-dev+unsubscribe@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/chromium-dev/4586235c-45b3-40b0-b440-73d7e1a7d5fc%40chromium.org.

[nat...@lenovo-chrome.com]

Yes, thanks. I even set them up again in case I messed something up the first time (it would not be unprecedented...) and the same thing happened.

[nat...@lenovo-chrome.com]

When the browser is built using the chromeos-chrome.9999 ebuild, is there a way to completely clean all the build products and start from scratch (I could probably suss this out from reading the ebuild file, but I'm still not great at understanding ebuilds and want to make sure I'm not missing anything). I feel my next step is to make sure none of the changes I made are still mistakenly getting included in my build.

(I could spin up a new chroot and create a new chromium git repository, but I live in New Zealand and sucking all those bits over the Pacific takes an absolute eternity, so I'd like to avoid that if possible....)