Installing firefox fails

[felixwatts]

Not sure if I'm doing something wrong but our build has recently started failing unexpectedly:

Orb version

1.4.1

What happened

At build step "Install Firefox", fails with output:

System detected as Linux
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed

  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
100   703  100   703    0     0  27038      0 --:--:-- --:--:-- --:--:-- 27038
Latest stable version of Firefox is 109.0.1

Exited with code exit status 100

Expected behavior

Build should succeed.

[justindbelanger]

I think we've started seeing the same issue with our builds on CircleCI. The build output looks like this:

System detected as Linux
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100   703  100   703    0     0   9451      0 --:--:-- --:--:-- --:--:--  9500
Latest stable version of Firefox is 109.0.1
A different version of Firefox is installed (Mozilla Firefox 107.0); removing it
^@^@

Exited with code exit status 100

CircleCI received exit code 100

We first started seeing this issue with version 1.3.0, but updating to 1.4.1 didn't fix the problem.

[justindbelanger]

As a work-around: hardcoding the Firefox version when performing the install-browser-tools step seems to fix the problem, for now.

      - browser-tools/install-browser-tools:
          firefox-version: "107.0"

[oroth8]

Started to see this happening today with circleci/browser-tools@1.1. I used @justindbelanger 's solution and it is performing successfully now.

[HennaAbbas]

@oroth8 @justindbelanger @felixwatts This issue was most likely related to the following incident: https://status.canonical.com/#/incident/KNms6QK9ewuzz-7xUsPsNylV20jEt5kyKsd8A-3ptQEVUe5iAwdm8JF7ErCrLqPnMAwu3z5Y-lH0alDAJSJH6w==

Can ya'll confirm it has been resolved?

[oroth8]

@oroth8 @justindbelanger @felixwatts This issue was most likely related to the following incident: status.canonical.com/#/incident/KNms6QK9ewuzz-7xUsPsNylV20jEt5kyKsd8A-3ptQEVUe5iAwdm8JF7ErCrLqPnMAwu3z5Y-lH0alDAJSJH6w==

Can ya'll confirm it has been resolved?

@HennaAbbas yes it is resolved now, probably safe to close this issue.

[BytesGuy]

Thanks for confirming! As this was related to the Canonical archive servers incident, which is resolved, I will now close this issue