Closed Serafadam closed 8 months ago
We can confirm the same for this issue:
Log:
Setting up netstandard-targeting-pack-2.1 (6.0.113-0ubuntu1~22.04.1) ...
Setting up dotnet-targeting-pack-6.0 (6.0.113-0ubuntu1~22.04.1) ...
Setting up aspnetcore-targeting-pack-6.0 (6.0.113-0ubuntu1~22.04.1) ...
Setting up aspnetcore-runtime-6.0 (6.0.113-0ubuntu1~22.04.1) ...
Setting up dotnet-hostfxr-6.0 (6.0.113-0ubuntu1~22.04.1) ...
Setting up powershell (7.3.3-1.deb) ...
Setting up grub-efi-amd64-bin (2.06-2ubuntu14.1) ...
Setting up grub-efi-amd64-signed (1.187.3~22.04.1+2.06-2ubuntu14.1) ...
mount: /var/lib/grub/esp: special device /dev/disk/by-id/scsi-14d534654202020200690df035523a242afc173af9e57f2a4-part15 does not exist.
dpkg: error processing package grub-efi-amd64-signed (--configure):
installed grub-efi-amd64-signed package post-installation script subprocess returned error exit status 32
Processing triggers for mailcap (3.70+nmu1ubuntu1) ...
Processing triggers for hicolor-icon-theme (0.17-2) ...
Processing triggers for man-db (2.10.2-1) ...
Errors were encountered while processing:
grub-efi-amd64-signed
needrestart is being skipped since dpkg has failed
E: Sub-process /usr/bin/dpkg returned an error code (1)
Error: The process '/usr/bin/sudo' failed with exit code 100
Job: https://github.com/eclipse-iceoryx/iceoryx/actions/runs/4260998839/jobs/7414824784
Thanks for the report.
I'm seeing the error too: https://github.com/ros2/ros2_tracing/actions/runs/4259543402/jobs/7411865548#step:3:179
Adding sudo apt-mark hold grub-efi-amd64-signed
to setup-ros
could be a temporary workaround, but a proper solution would be better.
Looks like this was a problem with Ubuntu 20.04 in the past:
Looks like this was a problem with Ubuntu 20.04 in the past:
Bug report for this instance here:
A temporary workaround is now available on master
, see #543
A temporary workaround is now available on
master
, see #543
This is now available in v0.6
.
Description
Hi! I'm not sure if this is related specifically to
setup-ros
, but some of actions on our repository have started failing atsetup-ros
step, I thought that this related to versions of actions, but updating them didn't change anything.Expected Behavior
Actions passing.
Actual Behavior
Actions fail with following error messages:
To Reproduce
As this involves Github runner, I guess best option is for me to retrigger those actions manually.
System (please complete the following information)
Github runner, you can check out workflow file here