Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Live website builds are failing #22222

Closed
sftim opened this issue Jun 30, 2020 · 7 comments
Closed

Live website builds are failing #22222

sftim opened this issue Jun 30, 2020 · 7 comments
Assignees
Labels
kind/bug Categorizes issue or PR as related to a bug. priority/critical-urgent Highest priority. Must be actively worked on as someone's top priority right now.

Comments

@sftim
Copy link
Contributor

sftim commented Jun 30, 2020

This is a Bug Report

Problem: Live website builds are failing

Additional Information:
/kind bug
/priority critical-urgent

@k8s-ci-robot k8s-ci-robot added kind/bug Categorizes issue or PR as related to a bug. priority/critical-urgent Highest priority. Must be actively worked on as someone's top priority right now. labels Jun 30, 2020
@sftim
Copy link
Contributor Author

sftim commented Jun 30, 2020

The upcoming-events shortcode queries Google Calendar, and this integration is failing causing the symptoms above.

@sftim
Copy link
Contributor Author

sftim commented Jun 30, 2020

Example error
6:37:21 PM: Build ready to start
6:37:23 PM: build-image version: 9d79ad851d6eff3969322d6e5b1df3d597650c41
6:37:23 PM: build-image tag: v3.3.19
6:37:23 PM: buildbot version: 8e2e5a3a5212190d0490c1372e313994f9085345
6:37:23 PM: Fetching cached dependencies
6:37:24 PM: Starting to download cache of 254.3KB
6:37:24 PM: Finished downloading cache in 84.064006ms
6:37:24 PM: Starting to extract cache
6:37:24 PM: Failed to fetch cache, continuing with build
6:37:24 PM: Starting to prepare the repo for build
6:37:24 PM: No cached dependencies found. Cloning fresh repo
6:37:24 PM: git clone https://github.com/kubernetes/website
6:37:38 PM: Preparing Git Reference pull/22198/head
6:37:41 PM: Different functions path detected, going to use the one specified in the Netlify configuration file: 'functions' versus '' in the Netlify UI
6:37:41 PM: Different build command detected, going to use the one specified in the Netlify configuration file: 'git submodule update --init --recursive --depth 1 && make deploy-preview' versus 'hugo' in the Netlify UI
6:37:41 PM: Starting build script
6:37:41 PM: Installing dependencies
6:37:41 PM: Python version set to 2.7
6:37:43 PM: Downloading and installing node v10.20.0...
6:37:43 PM: Downloading https://nodejs.org/dist/v10.20.0/node-v10.20.0-linux-x64.tar.xz...
6:37:43 PM: Computing checksum with sha256sum
6:37:43 PM: Checksums matched!
6:37:46 PM: Now using node v10.20.0 (npm v6.14.4)
6:37:46 PM: Started restoring cached build plugins
6:37:46 PM: Finished restoring cached build plugins
6:37:46 PM: Attempting ruby version 2.3.6, read from environment
6:37:47 PM: 
6:37:47 PM: ** WARNING **
6:37:47 PM: Using custom ruby version 2.3.6, this will slow down the build.
6:37:47 PM: To ensure fast builds, set the RUBY_VERSION environment variable, or .ruby-version file, to an included ruby version.
6:37:47 PM: Included versions: 2.7.1 2.6.2
6:37:47 PM: 
6:37:47 PM: Required ruby-2.3.6 is not installed - installing.
6:37:48 PM: Searching for binary rubies, this might take some time.
6:37:48 PM: Found remote file https://rvm_io.global.ssl.fastly.net/binaries/ubuntu/16.04/x86_64/ruby-2.3.6.tar.bz2
6:37:48 PM: Checking requirements for ubuntu.
6:37:49 PM: Requirements installation successful.
6:37:49 PM: ruby-2.3.6 - #configure
6:37:49 PM: ruby-2.3.6 - #download
6:37:50 PM: ruby-2.3.6 - #validate archive
6:38:01 PM: ruby-2.3.6 - #extract
6:38:07 PM: ruby-2.3.6 - #validate binary
6:38:08 PM: ruby-2.3.6 - #setup
6:38:09 PM: ruby-2.3.6 - #gemset created /opt/buildhome/.rvm/gems/ruby-2.3.6@global
6:38:11 PM: ruby-2.3.6 - #importing gemset /opt/buildhome/.rvm/gemsets/global.gems............................................................
6:38:11 PM: ruby-2.3.6 - #generating global wrappers.......
6:38:11 PM: ruby-2.3.6 - #gemset created /opt/buildhome/.rvm/gems/ruby-2.3.6
6:38:11 PM: ruby-2.3.6 - #importing gemsetfile /opt/buildhome/.rvm/gemsets/default.gems evaluated to empty gem list
6:38:12 PM: ruby-2.3.6 - #generating default wrappers.......
6:38:12 PM: Using /opt/buildhome/.rvm/gems/ruby-2.3.6
6:38:13 PM: Using ruby version 2.3.6
6:38:13 PM: Using PHP version 5.6
6:38:13 PM: 5.2 is already installed.
6:38:13 PM: Using Swift version 5.2
6:38:13 PM: Started restoring cached node modules
6:38:13 PM: Finished restoring cached node modules
6:38:13 PM: Installing NPM modules using NPM version 6.14.4
6:38:15 PM: npm WARN deprecated @types/form-data@2.5.0: This is a stub types definition. form-data provides its own type definitions, so you do not need this installed.
6:38:15 PM: npm WARN deprecated @types/p-cancelable@1.0.1: This is a stub types definition. p-cancelable provides its own type definitions, so you do not need this installed.
6:38:15 PM: npm WARN deprecated @types/p-retry@3.0.1: This is a stub types definition. p-retry provides its own type definitions, so you do not need this installed.
6:38:18 PM: npm WARN deprecated core-js@2.6.11: core-js@<3 is no longer maintained and not recommended for usage due to the number of issues. Please, upgrade your dependencies to the actual version of core-js@3.
6:38:20 PM: npm WARN deprecated chokidar@2.1.8: Chokidar 2 will break on node v14+. Upgrade to chokidar 3 with 15x less dependencies.
6:38:20 PM: npm WARN deprecated fsevents@1.2.13: fsevents 1 will break on node v14+ and could be using insecure binaries. Upgrade to fsevents 2.
6:38:21 PM: npm WARN deprecated resolve-url@0.2.1: https://github.com/lydell/resolve-url#deprecated
6:38:21 PM: npm WARN deprecated urix@0.1.0: Please see https://github.com/lydell/urix#deprecated
6:38:30 PM: > core-js@2.6.11 postinstall /opt/build/repo/node_modules/core-js
6:38:30 PM: > node -e "try{require('./postinstall')}catch(e){}"
6:38:30 PM: > uglifyjs-webpack-plugin@0.4.6 postinstall /opt/build/repo/node_modules/uglifyjs-webpack-plugin
6:38:30 PM: > node lib/post_install.js
6:38:30 PM: npm notice created a lockfile as package-lock.json. You should commit this file.
6:38:30 PM: npm WARN notsup Unsupported engine for watchpack-chokidar2@2.0.0: wanted: {"node":"<8.10.0"} (current: {"node":"10.20.0","npm":"6.14.4"})
6:38:30 PM: npm WARN notsup Not compatible with your version of node/npm: watchpack-chokidar2@2.0.0
6:38:30 PM: npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@~2.1.2 (node_modules/chokidar/node_modules/fsevents):
6:38:30 PM: npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@2.1.3: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
6:38:30 PM: npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@^1.2.7 (node_modules/watchpack-chokidar2/node_modules/chokidar/node_modules/fsevents):
6:38:30 PM: npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.2.13: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
6:38:30 PM: added 711 packages from 454 contributors and audited 713 packages in 16.542s
6:38:31 PM: 25 packages are looking for funding
6:38:31 PM:   run `npm fund` for details
6:38:31 PM: found 2 low severity vulnerabilities
6:38:31 PM:   run `npm audit fix` to fix them, or `npm audit` for details
6:38:31 PM: NPM modules installed
6:38:31 PM: Installing Hugo 0.70.0
6:38:32 PM: Hugo Static Site Generator v0.70.0-7F47B99E/extended linux/amd64 BuildDate: 2020-05-06T11:26:13Z
6:38:32 PM: Started restoring cached go cache
6:38:32 PM: Finished restoring cached go cache
6:38:32 PM: Installing Go version 1.10
6:38:41 PM: unset GOOS;
6:38:41 PM: unset GOARCH;
6:38:41 PM: export GOROOT='/opt/buildhome/.gimme_cache/versions/go1.10.linux.amd64';
6:38:41 PM: export PATH="/opt/buildhome/.gimme_cache/versions/go1.10.linux.amd64/bin:${PATH}";
6:38:41 PM: go version >&2;
6:38:41 PM: export GIMME_ENV="/opt/buildhome/.gimme_cache/env/go1.10.linux.amd64.env"
6:38:41 PM: go version go1.10 linux/amd64
6:38:41 PM: Installing missing commands
6:38:41 PM: Verify run directory
6:38:42 PM: ​
6:38:42 PM: ┌─────────────────────────────┐
6:38:42 PM: │        Netlify Build        │
6:38:42 PM: └─────────────────────────────┘
6:38:42 PM: ​
6:38:42 PM: ❯ Version
6:38:42 PM:   @netlify/build 2.0.20
6:38:42 PM: ​
6:38:42 PM: ❯ Flags
6:38:42 PM:   deployId: 5efb78515c29e1d227d9ef41
6:38:42 PM:   mode: buildbot
6:38:42 PM: ​
6:38:42 PM: ❯ Current directory
6:38:42 PM:   /opt/build/repo
6:38:42 PM: ​
6:38:42 PM: ❯ Config file
6:38:42 PM:   /opt/build/repo/netlify.toml
6:38:42 PM: ​
6:38:42 PM: ❯ Context
6:38:42 PM:   deploy-preview
6:38:43 PM: ​
6:38:43 PM: ┌────────────────────────────────────┐
6:38:43 PM: │ 1. build.command from netlify.toml │
6:38:43 PM: └────────────────────────────────────┘
6:38:43 PM: ​
6:38:43 PM: $ git submodule update --init --recursive --depth 1 && make deploy-preview
6:38:43 PM: Submodule 'assets/vendor/Font-Awesome' (https://github.com/FortAwesome/Font-Awesome.git) registered for path 'themes/docsy/assets/vendor/Font-Awesome'
6:38:43 PM: Submodule 'assets/vendor/bootstrap' (https://github.com/twbs/bootstrap.git) registered for path 'themes/docsy/assets/vendor/bootstrap'
6:38:43 PM: Cloning into '/opt/build/repo/themes/docsy/assets/vendor/Font-Awesome'...
6:38:45 PM: Cloning into '/opt/build/repo/themes/docsy/assets/vendor/bootstrap'...
6:38:50 PM: From https://github.com/FortAwesome/Font-Awesome
6:38:50 PM:  * branch            538a5bc4cf7989821d052e3ff919e2bead07021c -> FETCH_HEAD
6:38:50 PM: Submodule path 'themes/docsy/assets/vendor/Font-Awesome': checked out '538a5bc4cf7989821d052e3ff919e2bead07021c'
6:38:53 PM: From https://github.com/twbs/bootstrap
6:38:53 PM:  * branch            3b558734382ce58b51e5fc676453bfd53bba9201 -> FETCH_HEAD
6:38:53 PM: Submodule path 'themes/docsy/assets/vendor/bootstrap': checked out '3b558734382ce58b51e5fc676453bfd53bba9201'
6:38:53 PM: hugo --enableGitInfo --buildFuture -b https://deploy-preview-22198--kubernetes-io-master-staging.netlify.app
6:38:57 PM: Building sites … 
6:38:57 PM:   Replace Autoprefixer browsers option to Browserslist config.
6:38:57 PM:   Use browserslist key in package.json or .browserslistrc file.
6:38:57 PM:   Using browsers option can cause errors. Browserslist config
6:38:57 PM:   can be used for Babel, Autoprefixer, postcss-normalize and other tools.
6:38:57 PM:   If you really need to use option, rename it to overrideBrowserslist.
6:38:57 PM:   Learn more at:
6:38:57 PM:   https://github.com/browserslist/browserslist#readme
6:38:57 PM:   https://twitter.com/browserslist
6:38:57 PM: 
6:39:19 PM: ERROR 2020/06/30 17:39:19 Failed to get JSON resource "https://www.googleapis.com/calendar/v3/calendars/nt2tcnbtbied3l6gi2h29slvc0%40group.calendar.google.com/events?orderBy=startTime&singleEvents=true&timeMin=2020-06-30T17%3A39%3A18Z&key=AIzaSyAST-sCyPJzMQJSl6_vRPW9r4DNLPaDIyM": Failed to retrieve remote file: Unauthorized
6:39:20 PM: Total in 26711 ms
6:39:20 PM: Error: Error building site: "/opt/build/repo/content/en/community/_index.html:183:5": failed to render shortcode "upcoming-events": failed to process shortcode: "/opt/build/repo/layouts/shortcodes/upcoming-events.html:11:9": execute of template failed: template: shortcodes/upcoming-events.html:11:9: executing "shortcodes/upcoming-events.html" at : error calling first: both limit and seq must be provided
6:39:20 PM: Makefile:32: recipe for target 'deploy-preview' failed
6:39:20 PM: make: *** [deploy-preview] Error 255
6:39:20 PM: ​
6:39:20 PM: ┌─────────────────────────────┐
6:39:20 PM: │   "build.command" failed    │
6:39:20 PM: └─────────────────────────────┘
6:39:20 PM: ​
6:39:20 PM:   Error message
6:39:20 PM:   Command failed with exit code 2: git submodule update --init --recursive --depth 1 && make deploy-preview
6:39:20 PM: ​
6:39:20 PM:   Error location
6:39:20 PM:   In build.command from netlify.toml:
6:39:20 PM:   git submodule update --init --recursive --depth 1 && make deploy-preview
6:39:20 PM: ​
6:39:20 PM:   Resolved config
6:39:20 PM:   build:
6:39:20 PM:     command: git submodule update --init --recursive --depth 1 && make deploy-preview
6:39:20 PM:     environment:
6:39:20 PM:       - REVIEW_ID
6:39:20 PM:       - SLACK_WEBHOOK_URL
6:39:20 PM:       - HUGO_VERSION
6:39:20 PM:       - NODE_VERSION
6:39:20 PM:     functions: /opt/build/repo/functions
6:39:20 PM:     publish: /opt/build/repo/public
6:39:20 PM: Caching artifacts
6:39:20 PM: Started saving node modules
6:39:20 PM: Finished saving node modules
6:39:20 PM: Started saving build plugins
6:39:20 PM: Finished saving build plugins
6:39:20 PM: Started saving pip cache
6:39:20 PM: Finished saving pip cache
6:39:20 PM: Started saving emacs cask dependencies
6:39:20 PM: Finished saving emacs cask dependencies
6:39:20 PM: Started saving maven dependencies
6:39:20 PM: Finished saving maven dependencies
6:39:20 PM: Started saving boot dependencies
6:39:20 PM: Finished saving boot dependencies
6:39:20 PM: Started saving go dependencies
6:39:22 PM: Finished saving go dependencies
6:39:26 PM: Cached ruby version 2.3.6
6:39:26 PM: Error running command: Build script returned non-zero exit code: 1
6:39:26 PM: Failing build: Failed to build site
6:39:26 PM: Failed during stage 'building site': Build script returned non-zero exit code: 1
6:39:26 PM: Finished processing build request in 2m2.957558532s

from https://app.netlify.com/sites/kubernetes-io-master-staging/deploys/5efb78515c29e1d227d9ef41

@sftim
Copy link
Contributor Author

sftim commented Jun 30, 2020

/assign

(anyone else is very welcome to help with investigation)

@celestehorgan
Copy link
Contributor

@sftim https://www.netlifystatus.com/ netlify reported a minor incident earlier today. Related?

@sftim
Copy link
Contributor Author

sftim commented Jun 30, 2020

I don't think so. The problem seems to be that the website was using an API key to fetch a Google calendar during a build, and that fetch no longer works.

Possibly the API key has been deactivated, possibly that API was deprecated and now no longer functions. I will look into this a bit more.

@sftim
Copy link
Contributor Author

sftim commented Jun 30, 2020

This bug is fixed but the community page still needs fixing.
/close

@k8s-ci-robot
Copy link
Contributor

@sftim: Closing this issue.

In response to this:

This bug is fixed but the community page still needs fixing.
/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Categorizes issue or PR as related to a bug. priority/critical-urgent Highest priority. Must be actively worked on as someone's top priority right now.
Projects
None yet
Development

No branches or pull requests

3 participants