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

macOS-10.15 agent uses Homebrew 3.0.10 which uses Bintray #3165

Closed
1 of 7 tasks
thisisthekap opened this issue Apr 12, 2021 · 13 comments
Closed
1 of 7 tasks

macOS-10.15 agent uses Homebrew 3.0.10 which uses Bintray #3165

thisisthekap opened this issue Apr 12, 2021 · 13 comments
Labels
Area: Packages awaiting-deployment Code complete; awaiting deployment and/or deployment in progress OS: macOS

Comments

@thisisthekap
Copy link

Description

According to Homebrew/discussions#691, Homebrew switched from Bintray to GitHub Packages. Homebrew 3.1.0 uses the new CDN. The Microsoft Hosted Agents should imho be updated accordingly to avoid issues when downloading/installing packages using Homebrew.

Area for Triage:
Artifacts, Packages, Servers

Question, Bug, or Feature?:
Bug

Virtual environments affected

  • Ubuntu 16.04
  • Ubuntu 18.04
  • Ubuntu 20.04
  • macOS 10.15
  • macOS 11.0
  • Windows Server 2016 R2
  • Windows Server 2019
@maxim-lobanov
Copy link
Contributor

Hello @thisisthekap , I think nothing is required from our side to switch CDN.
As I can see, 5 hours ago the new version of brew with support of new CDN was released: https://github.com/Homebrew/brew/releases/tag/3.1.0

We will update Homebrew to this version with new image rollout (approx middle of next week since this week rollout has been already started).

@Darleev Darleev added OS: macOS Area: Packages awaiting-deployment Code complete; awaiting deployment and/or deployment in progress and removed needs triage labels Apr 12, 2021
@thisisthekap
Copy link
Author

@maxim-lobanov Thank you for the quick response!

Updating Homebrew to 3.1.0 is indeed the solution I was hoping for :)

Once again: Thank you very much 😎

@jsonfry
Copy link

jsonfry commented Apr 12, 2021

Right now bintray have started what they're calling a 'brown out' https://status.bintray.com/incidents/4mzph0y8l6hk
but actually means they're failing all requests to bintray for the next few hours, so any brew installs in macos runners are failing / will fail.

Did you have to update brew as part of your ci job?

@thisisthekap
Copy link
Author

I just execute brew update prior to the needed brew install call to make sure Homebrew is on the lastest version.

@jsonfry
Copy link

jsonfry commented Apr 12, 2021

Hmm not ideal.

@maxim-lobanov I guess there's no chance of brew being updated before bintray finished their thing in about 6 hours?

@jonathanhood
Copy link

Some kind of guidance, or a notification of some kind on the actions status page, may be necessary. It took me, at least, a good portion of the morning chasing down links to find myself here. Such a notification, email, or whatever could save a lot of people a lot of time this morning - especially since the brownout doesn't end until 2pm pacific.

@ColinPitrat
Copy link

ColinPitrat commented Apr 12, 2021

I'm seeing some "403 forbidden" when executing brew install today from GitHub Actions. Is this linked to this issue?

Adding logs to help discoverability of this issue:

Run brew install sdl2
==> Downloading https://homebrew.bintray.com/bottles/sdl2-2.0.14_1.catalina.bottle.tar.gz
curl: (22) The requested URL returned error: 403 Forbidden
Error: Failed to download resource "sdl2"

The workaround is to run brew update before brew install:

      - run: brew update
      - run: brew install sdl2

@jonathanhood
Copy link

jonathanhood commented Apr 12, 2021

Yes. To recap the issue:

  1. Bintray is issuing 403 Forbidden errors today as part of a scheduled "brownout" in preparation for their take down of the service.
  2. A version of brew is available that uses github packages instead. This version is not currently installed by default on the mac actions runners.

While we wait for the runners to be updated, you can do brew update manually in your github actions workflow and sidestep the issue.

@mathbagu
Copy link

When can we expect the runners to be updated, just to know if we should use the suggested workaround?

@miketimofeev
Copy link
Contributor

@mathbagu we've decided to start the new rollout tomorrow to deliver the fix asap

@maxim-lobanov
Copy link
Contributor

Issue is related to planned brown-out session on Bintray side.
Bintray is going to recover in a few hours so issue should disappear: https://status.bintray.com/incidents/4mzph0y8l6hk

With next image rollout, homebrew should stop using bintray. Updating runners take about 3-4 days usually.

brendongo added a commit to semgrep/semgrep that referenced this issue Apr 12, 2021
homebrew uses Github package to distribute package instead of bintray but the github action
isnt updated yet. Workaround is to update homebrew before calling install

Relevant links:
Homebrew/discussions#691
actions/runner-images#3165
Homebrew/brew#11070
brendongo added a commit to semgrep/semgrep that referenced this issue Apr 12, 2021
homebrew uses Github package to distribute package instead of bintray but the github action
isnt updated yet. Workaround is to update homebrew before calling install

Relevant links:
Homebrew/discussions#691
actions/runner-images#3165
Homebrew/brew#11070
@maxim-lobanov
Copy link
Contributor

The deployment of new set of images has been already started and will be finished in a few days.

@miketimofeev
Copy link
Contributor

@thisisthekap We have deployed macOS images with brew 3.1.1 on board! All the packages are now retrieved from GitHub Packages.
I'm going to close the issue. Please feel free to contact us if you have any concerns.
Thank you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area: Packages awaiting-deployment Code complete; awaiting deployment and/or deployment in progress OS: macOS
Projects
None yet
Development

No branches or pull requests

8 participants