I have suddenly some problems building my Gatsby App, here are the logs :
4:17:12 PM: Build ready to start
4:17:14 PM: build-image version: c6001ed68662a13e5deb24abec2b46058c58248a
4:17:14 PM: build-image tag: v3.9.0
4:17:14 PM: buildbot version: 1523fa12d6de79e532ed0aff71973c5fbb8e58aa
4:17:14 PM: Building without cache
4:17:14 PM: Starting to prepare the repo for build
4:17:15 PM: No cached dependencies found. Cloning fresh repo
4:17:15 PM: git clone https://github.com/XXXXXXXXXXX/XXXXXXXXX
4:17:16 PM: Preparing Git Reference refs/heads/pre-prod
4:17:17 PM: Parsing package.json dependencies
4:17:18 PM: Starting build script
4:17:18 PM: Installing dependencies
4:17:18 PM: Python version set to 2.7
4:17:19 PM: Downloading and installing node v14.17.5...
4:17:19 PM: Downloading https://nodejs.org/dist/v14.17.5/node-v14.17.5-linux-x64.tar.xz...
4:17:20 PM: Computing checksum with sha256sum
4:17:20 PM: Checksums matched!
4:17:23 PM: Now using node v14.17.5 (npm v6.14.14)
4:17:23 PM: Started restoring cached build plugins
4:17:23 PM: Finished restoring cached build plugins
4:17:23 PM: Attempting ruby version 2.7.2, read from environment
4:17:25 PM: Using ruby version 2.7.2
4:17:25 PM: Using PHP version 5.6
4:17:25 PM: Started restoring cached yarn cache
4:17:25 PM: Finished restoring cached yarn cache
4:17:25 PM: Installing yarn at version 1.22.10
4:17:25 PM: Installing Yarn!
4:17:25 PM: > Downloading tarball...
4:17:25 PM: [1/2]: https://yarnpkg.com/downloads/1.22.10/yarn-v1.22.10.tar.gz --> /tmp/yarn.tar.gz.ESuoC3cTNW
4:17:25 PM: % Total % Received % Xferd Average Speed Time Time Time Current
4:17:25 PM: Dload Upload Total Spent Left Speed
4:17:26 PM: 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
4:17:26 PM: 100 81 100 81 0 0 228 0 --:--:-- --:--:-- --:--:-- 228
4:17:26 PM: 100 81 100 81 0 0 228 0 --:--:-- --:--:-- --:--:-- 228
4:17:26 PM: 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
4:17:26 PM: curl: (60) server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
4:17:26 PM: More details here: http://curl.haxx.se/docs/sslcerts.html
4:17:26 PM: curl performs SSL certificate verification by default, using a "bundle"
of Certificate Authority (CA) public keys (CA certs). If the default
4:17:26 PM: bundle file isn't adequate, you can specify an alternate file
4:17:26 PM: using the --cacert option.
4:17:26 PM: If this HTTPS server uses a certificate signed by a CA represented in
4:17:26 PM: the bundle, the certificate verification probably failed due to a
4:17:26 PM: problem with the certificate (it might be expired, or the name might
4:17:26 PM: not match the domain name in the URL).
4:17:26 PM: If you'd like to turn off curl's verification of the certificate, use
4:17:26 PM: the -k (or --insecure) option.
4:17:26 PM: [2/2]: https://yarnpkg.com/downloads/1.22.10/yarn-v1.22.10.tar.gz.asc --> /tmp/yarn.tar.gz.ESuoC3cTNW.asc
4:17:26 PM: 100 85 100 85 0 0 1506 0 --:--:-- --:--:-- --:--:-- 1506
4:17:26 PM: 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
4:17:26 PM: curl: (60) server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
4:17:26 PM: More details here: http://curl.haxx.se/docs/sslcerts.html
4:17:26 PM: curl performs SSL certificate verification by default, using a "bundle"
of Certificate Authority (CA) public keys (CA certs). If the default
4:17:26 PM: bundle file isn't adequate, you can specify an alternate file
4:17:26 PM: using the --cacert option.
4:17:26 PM: If this HTTPS server uses a certificate signed by a CA represented in
4:17:26 PM: the bundle, the certificate verification probably failed due to a
4:17:26 PM: problem with the certificate (it might be expired, or the name might
4:17:26 PM: not match the domain name in the URL).
4:17:26 PM: If you'd like to turn off curl's verification of the certificate, use
4:17:26 PM: the -k (or --insecure) option.
4:17:26 PM: > Failed to download https://yarnpkg.com/downloads/1.22.10/yarn-v1.22.10.tar.gz.
4:17:26 PM: mv: cannot stat '/opt/buildhome/.yarn': No such file or directory
4:17:26 PM: No yarn workspaces detected
4:17:26 PM: Started restoring cached node modules
4:17:26 PM: Finished restoring cached node modules
4:17:26 PM: /opt/build-bin/run-build-functions.sh: line 141: yarn: command not found
4:17:26 PM: Installing NPM modules using Yarn version
4:17:27 PM: /opt/build-bin/run-build-functions.sh: line 152: yarn: command not found
4:17:27 PM: Error during Yarn install
4:17:27 PM: Build was terminated: Build script returned non-zero exit code: 1
4:17:27 PM: Creating deploy upload records
4:17:27 PM: Failing build: Failed to build site
4:17:27 PM: Failed during stage 'building site': Build script returned non-zero exit code: 1
4:17:27 PM: Finished processing build request in 13.005414871s
Hi there, @DaNG Thanks so much for sharing this. Our Engineers have been notified and are digging in to this. I will update this thread as soon as I have further information.
In the interim, if you switch your build image to Focal does that mitigate the issue?
As an update: Builds using the Xenial and Trusty versions of our build image (configured in each site’s Deploy Settings page) that require a download of yarn are failing. This will impact only builds without an already-cached copy of yarn. We’re working on a fix but in the meantime, builds on our newer (default) Focal build image are not affected; you can update to the new image to work around this immediately.
@jomoka I’m glad to hear that updating to Focal fixed the Yarn installation issue. Unfortunately, it seems you’ve now run into a dependency mismatch with the Focal’s available installed software.
We have a build image migration guide with general troubleshooting steps for updating build images. It may take a few more builds to figure out, but on the plus side, once you’re building successfully on Focal, you can stay there. The Xenial build image will be scheduled for deprecation in the next few months, so you’ll have a head start on that. Or you can wait for this incident to be resolved, which we’re hoping should happen fairly soon.
A fix has been implemented. The mitigation is automatic on Xenial, but Trusty sites will have to update to Xenial or Focal in order to mitigate. We’ll continue to monitor for a while before resolving the incident. As always, you can view our Status Page here.
Thanks so much for sharing this. Our Engineers have been notified and are digging in to this. I will update this thread as soon as I have further information.
