-
Notifications
You must be signed in to change notification settings - Fork 3.3k
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
Ubuntu 24.04 jobs directly fail after installing libssl-dev package #9937
Comments
Log file |
Confirmed. This is due to pulling See |
I moved to 24.04 because on 22.04 gcc13 was removed (#9866), probably this will hit more users |
This should be reverted once the core issue has been resolved: actions/runner-images#9937
This should be reverted once the core issue has been resolved: actions/runner-images#9937
This should be reverted once the core issue has been resolved: actions/runner-images#9937
I'm actually hitting the same issue, on my fork of actions/python-version, because it has 'libssl-dev' in there: https://github.com/actions/python-versions/blob/c990e6da9586f6b33bf19aba61c934ded6ec28c5/builders/ubuntu-python-builder.psm1#L71 i've tried setting combinations of these env vars to no avail:
In the end I, ahem, did |
I used "sudo apt install --no-upgrade ..." as workaround/solution. |
Workafound |
This is IMO the only real solution for GitHub runners: Any package upgrade from So remove PR up: #9956 |
since it triggers a restart of all systemd services, including the `runner-provisioner`, crashing the workflow, whenever packages from the OpenSSL/LibSSL package source are upgraded. Solves: actions#9937 Signed-off-by: MichaIng <[email protected]>
Hi @jwillemsen , We're unable to re-produce the error , Please retry it now by forking the main branch . |
@kishorekumar-anchala What? I takes little effort to reproduce.
Looking above, you also have like 10 linked pull request to repos experiencing the same issue. |
Hi @jmarrec , Could you please try with latest ubuntu image build: |
@kishorekumar-anchala Within a GitHub Actions workflow run, it must never happen that all systemd services are restarted, the |
fixed and rolled now. |
Another try (try every env var) for actions/runner-images#9937 https://github.com/liske/needrestart/blob/d3e33025543cc8459e470379a38c967c362cd4df/man/needrestart.1#L71-L73 Another try with DEBIAN_FRONTEND Try to apt remove needrestart complelely
This reverts commit bcfac4118b1177f5bfae530a3eb118fe823b6932.
Another try (try every env var) for actions/runner-images#9937 https://github.com/liske/needrestart/blob/d3e33025543cc8459e470379a38c967c362cd4df/man/needrestart.1#L71-L73 Another try with DEBIAN_FRONTEND Try to apt remove needrestart complelely
This reverts commit bcfac4118b1177f5bfae530a3eb118fe823b6932.
Description
I am adding gcc13 to ubuntu 24.04 using
Directly after this the jobs all fail with
See https://github.com/RemedyIT/taox11/actions/runs/9252204973/job/25449380677?pr=387
Platforms affected
Runner images affected
Image version and build link
20240516.4.0
Is it regression?
Yes
Expected behavior
Job runs
Actual behavior
Job fails
Repro steps
See the taox11 repo at https://github.com/RemedyIT/taox11
The text was updated successfully, but these errors were encountered: