cros_sdk met some issues

Skip to first unread message


Nov 23, 2021, 10:56:06 PM11/23/21
to Chromium OS Development

Hi everyone ~

Recently I'm trying to setup an environment for chromium OS.
I repo sync the source code successfully but during cros_sdk, I met some issues.
During the cros_sdk, it shows below error:
gs_fetch_binpkg: Unhandled exception:
Traceback (most recent call last):
  File "/mnt/host/source/chromite/lib/", line 418, in RunCurl
    stderr=True, extra_env={'LC_MESSAGES': 'C'}, *args, **kwargs)
  File "/mnt/host/source/chromite/lib/", line 359, in RunCommandWithRetries
    return RetryCommand(, max_retry, *args, **kwargs)
  File "/mnt/host/source/chromite/lib/", line 331, in RetryCommand
    return GenericRetry(ShouldRetry, max_retry, functor, *args, **kwargs)
  File "/mnt/host/source/chromite/lib/", line 250, in GenericRetry
    return _run()
  File "/mnt/host/source/chromite/lib/", line 220, in _Wrapper
    raise exc_info[1].with_traceback(exc_info[2])
  File "/mnt/host/source/chromite/lib/", line 183, in _Wrapper
    ret = func(*args, **kwargs)
  File "/mnt/host/source/chromite/lib/", line 249, in _run
    return functor(*args, **kwargs)
  File "/mnt/host/source/chromite/lib/", line 921, in run
    raise RunCommandError(msg, cmd_result)
chromite.lib.cros_build_lib.RunCommandError: return code: 60; command: curl --http1.1 --fail -o /home/hle4sgh/Work/Google/ChromiumOS/code/.cache/common/staging/tarball-cacheif3bdnxf/gsutil_5.4.tar.gz
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
  0     0    0     0    0     0      0      0 --:--:--  0:00:01 --:--:--     0
curl: (60) SSL certificate problem: self signed certificate in certificate chain
More details here:

curl failed to verify the legitimacy of the server and therefore could not
establish a secure connection to it. To learn more about this situation and
how to fix it, please visit the web page mentioned above.

cmd=['curl', '--http1.1', '--fail', '', '-o', '/home/hle4sgh/Work/Google/ChromiumOS/code/.cache/common/staging/tarball-cacheif3bdnxf/gsutil_5.4.tar.gz'], extra env={'LC_MESSAGES': 'C'}

However, I tried to run this cmd in another terminal, it succeeded:
~$ curl --http1.1 --fail -o    ./gsutil_5.4.tar.gz
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100 3934k  100 3934k    0     0   708k      0  0:00:05  0:00:05 --:--:--  827k
~$ ll gsutil_5.4.tar.gz
-rw-r--r--  1 leo leo 3.9M Nov 24 09:53 gsutil_5.4.tar.gz

So, can anyone give me some work around or the reason?


Brian Norris

Nov 29, 2021, 1:36:01 PM11/29/21
to Leo HUANG, Chromium OS Development
Any chance you're working on a corporate network where your IT department is replacing HTTPS certificates? If so, you're likely in sketchy territory and will have to self-help a bit. Searching around the bug tracker, it looks like people have managed to push their corporate CAs somewhere into the SDK's trust chain, but I don't have official advice on how to do that.

Chromium OS Developers mailing list:
View archives, change email options, or unsubscribe:

Peter Marheine

Nov 29, 2021, 5:54:33 PM11/29/21
to Brian Norris, Leo HUANG, Chromium OS Development
This looks like another "access to GCS from China" issue, similar to Leo's last problem. I'm not familiar with any workarounds though.
Reply all
Reply to author
0 new messages