[bug] gatsby.2.23.3/2.23.4 failing in Github Actions ubuntu 18 LTS

[JustFly1984]

@pieh I have got this error 3 times today in github actions build pipeline

$ yarn develop
$ gatsby develop -S
info setting up automatic SSL certificate (may require elevated permissions/sudo)

rm: cannot remove '/usr/local/share/ca-certificates/devcert.crt': No such file or directory
Picked up JAVA_TOOL_OPTIONS: -Dfile.encoding=UTF8

WARNING: apt does not have a stable CLI interface. Use with caution in scripts.

E: Failed to fetch http://security.ubuntu.com/ubuntu/pool/universe/n/nss/libnss3-tools_3.35-2ubuntu2.7_amd64.deb  404  Not Found [IP: 52.165.132.12 80]
E: Unable to fetch some archives, maybe run apt-get update or try with --fix-missing?
error Failed to generate dev SSL certificate


  Error: Command failed: sudo apt install libnss3-tools
  WARNING: apt does not have a stable CLI interface. Use with caution in scripts  .
  E: Failed to fetch http://security.ubuntu.com/ubuntu/pool/universe/n/nss/libns  s3-tools_3.35-2ubuntu2.7_amd64.deb  404  Not Found [IP: 52.165.132.12 80]
  E: Unable to fetch some archives, maybe run apt-get update or try with --fix-m  issing?
  
  - utils.js:22 Object.run
    [poolotto-gatsby]/[devcert]/dist/utils.js:22:28

After restarting failed task, deploy succeed.
Updating to 2.23.4 to check if it fixed.

Update: 2.23.4 also has same issue as 2.23.3
Update: reverting to 2.23.2 did not help,
pinning devcert to 1.1.0 helped only on local macos environment

[JustFly1984]

reverting back to 2.23.2 does not help, same error at runtime:

[JustFly1984]

Issue is related to #25064, but pinning devcert to 1.1.0 does not help in ubumtu environment.

[LekoArts]

Thanks for the issue! But as per #25064 (comment) this isn’t an issue with Gatsby but your GitHub actions setup.

[JustFly1984]

@LekoArts it is not issue of github actions setup, it is the issue of gatsby, due it having dependency devcert unpinned version, and reliance of devcert on environment to have certain modules installed by default, which happens is not reliable. We had this github actions setup for last 4 months at least and everything worked perfectly with ubuntu-latest as test/deploy target. Something has changed, and it bubbled up to gatsby. We had switched github actions target to macos-latest, and pined devcert to 1.1.0, and fixed ci pipelines.