Browser-tools orb install-chrome step fails pulling debian repository

Ecosystem Orbs
,
1

We’re using circleci orbs for installing chrome before running UI tests. And this error popped up today on our builds. Our last successful build was on Aug 11th. Here’s a snippet of the circleci config we have in place and the error message


version: 2.1

ruby_docker: &ruby_docker
  image: circleci/ruby:2.5.7-node
  environment:
    DATABASE_URL: "redacted"
    ELASTICSEARCH_URL: 'redacted'
    ELASTICSEARCH_HOST: 'redacted'
    ELASTICSEARCH_PORT: 'redacted'
    CI: true
...
...
orbs:
  browser-tools: circleci/browser-tools@1.1.1
  integration:
    docker:
      - *ruby_docker
      - image: circleci/mysql:5.7
      - image: circleci/redis:3.2
      - image: docker.elastic.co/elasticsearch/elasticsearch:7.3.1
        environment:
        - discovery.type: single-node
    steps:
      - browser-tools/install-chrome
      - browser-tools/install-chromedriver

Google Chrome is not currently installed; installing it
Get:1 http://deb.debian.org/debian buster InRelease [122 kB]
Get:2 http://security.debian.org/debian-security buster/updates InRelease [65.4 kB]
Get:3 http://deb.debian.org/debian buster-updates InRelease [51.9 kB]
Reading package lists... Done      
E: Repository 'http://security.debian.org/debian-security buster/updates InRelease' changed its 'Suite' value from 'stable' to 'oldstable'
N: This must be accepted explicitly before updates for this repository can be applied. See apt-secure(8) manpage for details.
N: Repository 'http://deb.debian.org/debian buster InRelease' changed its 'Version' value from '10.3' to '10.10'
E: Repository 'http://deb.debian.org/debian buster InRelease' changed its 'Suite' value from 'stable' to 'oldstable'
N: This must be accepted explicitly before updates for this repository can be applied. See apt-secure(8) manpage for details.
E: Repository 'http://deb.debian.org/debian buster-updates InRelease' changed its 'Suite' value from 'stable-updates' to 'oldstable-updates'
N: This must be accepted explicitly before updates for this repository can be applied. See apt-secure(8) manpage for details.

Exited with code exit status 100
CircleCI received exit code 100
2

I created a PR for a possible fix. Allow updates when release info changes by h-parekh · Pull Request #25 · CircleCI-Public/browser-tools-orb · GitHub</ti

3

Hi @thekatertot! I’m not sure how to follow up with code owners on this PR. Allow updates when release info changes by h-parekh · Pull Request #25 · CircleCI-Public/browser-tools-orb · GitHub</ti

Is there a better way than just commenting on the PR?

1 Like
4

I think that’s the best way for now. We are a little short staffed so it takes a little patience, but I’ll check in and see if they have any advice for now.

1 Like
5

I answered in the GitHub Issue.

1 Like