Actions runner image scheduled maintenance (June 2 2023 through June 16 2023)

[mikhailkoliada]

Breaking changes

Customers may see differences in the software versions installed in their runners between runs of the same workflow or pipeline.

Target date

Images will be up to date and consistent by June 16th 2023.

The motivation for the changes

The GitHub Runner Images team is extending the rollout of new image versions to provide a more predictable environment.

Possible impact

During this period you may see different runner image versions reported in your workflow runs or pipeline jobs. Versions may differ between runs or multiple attempts of the same run.

Platforms affected

• Azure DevOps
• GitHub Actions

Runner images affected

• Ubuntu 20.04
• Ubuntu 22.04
• macOS 11
• macOS 12
• macOS 13
• Windows Server 2019
• Windows Server 2022

Mitigation ways

No steps should be taken.

[codeArtisanry]

Hey there,
I guess I'm getting affected
Here is the detailed version of details you can see
#7659

I tried every Ubuntu image (22,20,18,lts) every time I'm getting the same error even in self hosted runner
Could you please able to give me any other Images for the workout ??

Any help is much appreciated...
Thanks

[mikhailkoliada]

It was decided to prolong the maintenance period up until June 16th to provide better experience in the future.

[renemadsen]

It was decided to prolong the maintenance period up until June 16th to provide better experience in the future.

@mikhailkoliada when will we be seeing the new ubuntu 22.04 images in our action runs? '
Right now it's always the former version Ubuntu 22.04 (20230517.1) and not the new Ubuntu 22.04 (20230604.1).

What does this maintenance period do in exact terms of experience?

May you in the future consider using different YAML Label for newest versions, so we don't have to be in this kind of limbo in the future when changes are done to the versions of software in the images. It's making it hard to have a consistent build env, when one cannot count on what version are in the build process. Hope it makes sense.

[modosc]

we started seeing job failures today. our jobs all use:

    runs-on: ubuntu-latest

we're seeing random failures with this message:

is this related to the rollout?

[lucaspopp-wbd]

+1 I am seeing similar issues using ubuntu-20.04 despite some jobs using that same runner passing

[OPattinson]

In the latest 22.04 image version (20230611.1) that has been rolled out, we are now experiencing ModuleNotFound errors when trying to import certain packages in Python3.8, even though the logs show that package has been downloaded and installed via Pip (specifically, the package dunamai-1.17.0, using latest version of pip).

The previous image version that we had running worked fine (20230517.1), so I'm assuming this is a result of the runner update?

[nikhaxuall]

^ I am seeing the same issue with ModuleNotFound errors in python3.8. Jobs that ran fine yesterday on ubuntu-20.04:20230517.1 fail when rerun today on 20230611.1

[vpolikarpov-akvelon]

@OPattinson, @nikhaxuall, current update rollouts for Ubuntu 20.04 and Ubuntu 22.04 runners have been completed:

• Ubuntu 20.04 (20230611) Image Update #7702
• Ubuntu 22.04 (20230611) Image Update #7701

If you see any problems that may be caused by this update please create a separate issue and provide more details (logs, workflow run links, repro steps, etc).

[mariokoehler]

with the new ubuntu image we see problems running our Arquillian Junit tests. the maven surefire plugin indicates that it has run the tests, but the actual test is not really executed (debug logs normally written by the test show up nowhere, and files that should have been created by the tests are missing, thats why we are certain the test hasn't actually run). we hand random individual builds that still pulled the old image and they were fine, but whenever the new image gets pulled this behavior appears.

[ciaranbrowne44]

@mikhailkoliada when today will the images be up to date and consistent? We are experiencing Typescript versioning issues in GH. In our workflow, we specify Typescript version 5.0.4 but in GH during compilation, (lodash incompatible) version 5.1.3 is selected.

[mikhailkoliada]

It has ended, runners should receive a standard updates cycle!