1622827 - Update to Google Chrome v81 in production

Status: RESOLVED FIXED

(Infrastructure & Operations :: RelOps: Puppet, task, P2)

Description

[Greg Mierzwinski [:sparky]]

Google chrome is being updated tomorrow to v81 so we'll have to update it in production.

Chromedriver's are being added in bug 1622825, and after they land, we can update.

Comment 1

[Greg Mierzwinski [:sparky]]

:dhouse, this update can happen at any time now, the chromedrivers have landed.

Comment 2

[:dhouse]

Thanks! I'll set up an update for the hardware workers.

Comment 3

[:dhouse]

:sparky, I see version 80.0.3987.149 released on 03.17. Although it is not v81, do you want this update applied?

https://chromiumdash.appspot.com/fetch_releases?channel=Stable&platform=Mac
https://chromiumdash.appspot.com/fetch_releases?channel=Stable&platform=Linux

Comment 4

[Greg Mierzwinski [:sparky]]

Oh sorry! They seem to have pushed the release date. I'll keep an eye on it and let you know when v81 is available, we don't need to do the minor version update.

Comment 5

[:dhouse]

Thanks!

Comment 6

[Greg Mierzwinski [:sparky]]

:dhouse it looks like chrome v81 has finally been released and we can start updating it.

Comment 7

[:dhouse]

Steps to prepare update before PR's:

1. Manual download of binaries from:
   https://www.google.com/chrome/browser/?platform=linux
   https://www.google.com/chrome/browser/?platform=mac

2. Check release version:
   from https://chromiumdash.appspot.com/fetch_releases?channel=Stable&platform=Linux
   https://chromiumdash.appspot.com/fetch_releases?channel=Stable&platform=Mac (https://earthangel-b40313e5.influxcloud.net/d/6brPJRoZk/wip-releases?orgId=1)
   81.0.4044.129

3. Upload binaries with corrected names (version put into filenames):
   for linux64 to build-puppet /data:

~$ scp /Users/house/Downloads/google-chrome-stable_v81.0.4044.129_amd64.deb rejh2.srv.releng.mdc1.mozilla.com:~/
[...]
[[e-mail] google_chrome]$ grep Version dists/xenial/all/binary-amd64/Packages
Version: 80.0.3987.106-1
Version: 81.0.4044.129-1
Version: 76.0.3809.132-1
Version: 79.0.3945.117-1

MacOS to s3 for ronin-puppet:

$ aws s3 cp ./googlechrome_v81.0.4044.129.dmg s3://ronin-puppet-package-repo/macos/public/10.14/

Comment 8

[:dhouse]

Attachment: macos mojave update

Comment 9

[:dhouse]

I updated the bitbar macbookpros' branch and they will pick up the update on their next reboot (https://firefox-ci-tc.services.mozilla.com/provisioners/releng-hardware/worker-types/gecko-t-osx-1014-power)

Comment 10

[:dhouse]

Attachment: linux64 chrome v81

Comment 11

[:dhouse]

:sparky, here are small linux64 and macos hardware pools if you want to run tests against them for verifying the google chrome v81 update. Let me know when you're ready for me to update the production pools (the pr's are ready to be merged).
linux64:
https://firefox-ci-tc.services.mozilla.com/provisioners/releng-hardware/worker-types/gecko-t-linux-talos-beta
macos:
https://firefox-ci-tc.services.mozilla.com/provisioners/releng-hardware/worker-types/gecko-t-osx-1014-beta
and I've updated the mbp power machines

re: bug 1628381 with android chrome installs through tooltool. I'm interested in doing the same for linux, and turning on chrome's auto-update for macos. What do you think?

Comment 12

[Greg Mierzwinski [:sparky]]

Thanks :dhouse! I've started a test run here: https://treeherder.mozilla.org/#/jobs?repo=try&revision=80d5a85f6732b372e19ddb31000fa1d1d8fdee5c

Regarding the tooltool switch, for linux I think that would be excellent and turning on auto-updates for Mac seems fine to me. One thing I've been wondering about is if for Mac (& Windows as well), do we have the ability to downgrade the chrome version if needed?

Comment 13

[:dhouse]

(In reply to Greg Mierzwinski [:sparky] from comment #12)

Thanks :dhouse! I've started a test run here: https://treeherder.mozilla.org/#/jobs?repo=try&revision=80d5a85f6732b372e19ddb31000fa1d1d8fdee5c

Regarding the tooltool switch, for linux I think that would be excellent and turning on auto-updates for Mac seems fine to me. One thing I've been wondering about is if for Mac (& Windows as well), do we have the ability to downgrade the chrome version if needed?

That test run looks like it completed successfully. I'll plan to do the switch tomorrow. Is that okay?

Re: auto-updates, I think we'll be able to downgrade on Macos as the install replaces the directory. I'll make a bug for turning the auto-update back on, and test a downgrade first (starting with v76, allowing autoupgrade, and then downgrading it). I'll make a note for checking that in Windows too.

Comment 14

[Greg Mierzwinski [:sparky]]

So the mac chrome tests failed but it's because of a worker configuration error. The linux tests ran well though so I'm comfortable with proceeding with the update on both platforms (I imagine the mac ones will be fine with the non-beta workers).

Comment 15

[:dhouse]

(In reply to Greg Mierzwinski [:sparky] from comment #14)

So the mac chrome tests failed but it's because of a worker configuration error. The linux tests ran well though so I'm comfortable with proceeding with the update on both platforms (I imagine the mac ones will be fine with the non-beta workers).

Thanks. I'll merge the change and herd the macos and linux workers through the update. I'll comment on this bug with progress and when complete.

Comment 16

[:dhouse]

linux64 is down to less than 10 with the old version (v80.0).
macos is at about half updated.

Comment 17

[:dhouse]

The updates applied correctly across most of the pools. I am manually checking the remaining workers not yet on v81 (count):
gecko-t-linux-talos 1
gecko-t-osx-1014 6
gecko-t-osx-1014-power 0

Comment 18

[:dhouse]

All of gecko-t-linux-talos and gecko-t-osx-1014 hardware workers are updated to chrome v81. The last few I fixed since my update yesterday were not running production tasks (dev/stage instead).