GHES 3.14 Upgrades runner to 2.317.0, this breaks ALL workflows on RHEL 7

[chadhutchins182]

Describe the bug
Node20 which is the default for action/runner since version 2.317.0 does not work on RHEL 7 (and this has been reported to not work for a few other flavors of linux)

This issue has been reported extensively (#337 #801 #2115 #2906 #3373) but GitHub Enterprise Server has been immune until the recent release of version 3.14.

It appears that there is a open PR #3128 to address this, however that PR is stale.

To Reproduce
Run any job on RHEL 7

Expected behavior
For the runner to run on RHEL 7

Runner Version and Platform

Version of your runner?
2.317.0

OS of the machine running the runner?
Red Hat Enterprise Linux 7

What's not working?

Any job that runs on a RHEL 7 machine using runner version 2.317.0

Job Log Output

Post job cleanup.
[2](https://github.nrlmry.navy.mil/ADP/adp-preprocessors/actions/runs/145159/job/193122#step:10:2)/users/blaylock/action-runners/runner_adp-preprocessors/externals/node20/bin/node: /lib64/libm.so.6: version `GLIBC_2.27' not found (required by /users/blaylock/action-runners/runner_adp-preprocessors/externals/node20/bin/node)
[3](https://github.nrlmry.navy.mil/ADP/adp-preprocessors/actions/runs/145159/job/193122#step:10:3)/users/blaylock/action-runners/runner_adp-preprocessors/externals/node20/bin/node: /lib64/libstdc++.so.6: version `GLIBCXX_3.4.20' not found (required by /users/blaylock/action-runners/runner_adp-preprocessors/externals/node20/bin/node)
[4](https://github.nrlmry.navy.mil/ADP/adp-preprocessors/actions/runs/145159/job/193122#step:10:4)/users/blaylock/action-runners/runner_adp-preprocessors/externals/node20/bin/node: /lib64/libstdc++.so.6: version `CXXABI_1.3.9' not found (required by /users/blaylock/action-runners/runner_adp-preprocessors/externals/node20/bin/node)
[5](https://github.nrlmry.navy.mil/ADP/adp-preprocessors/actions/runs/145159/job/193122#step:10:5)/users/blaylock/action-runners/runner_adp-preprocessors/externals/node20/bin/node: /lib64/libstdc++.so.6: version `GLIBCXX_3.4.21' not found (required by /users/blaylock/action-runners/runner_adp-preprocessors/externals/node20/bin/node)
[6](https://github.nrlmry.navy.mil/ADP/adp-preprocessors/actions/runs/145159/job/193122#step:10:6)/users/blaylock/action-runners/runner_adp-preprocessors/externals/node20/bin/node: /lib64/libc.so.6: version `GLIBC_2.28' not found (required by /users/blaylock/action-runners/runner_adp-preprocessors/externals/node20/bin/node)
[7](https://github.nrlmry.navy.mil/ADP/adp-preprocessors/actions/runs/145159/job/193122#step:10:7)/users/blaylock/action-runners/runner_adp-preprocessors/externals/node20/bin/node: /lib64/libc.so.6: version `GLIBC_2.25' not found (required by /users/blaylock/action-runners/runner_adp-preprocessors/externals/node20/bin/node)

[stefansli]

Setting environment variable ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION to true disables the forced update in runner versions 2.315.0 until 2.320.0.

Initially this was introduced by #3192 . The change, that the associated feature flag was activated with GHES 3.14 is missing from the GHES 3.14 release notes.

[thebollywoodguy]

@stefansli Is there any documentation about the feature flag and environment variable to be set that we can send to the customer? Omnissa (formerly VMWare EUC) is going to largely benefit by this.

[stefansli]

I'm just a user that was caught off guard, like you.

What pointed me in the right direction was this blog post that get's linked by a warning when running node16 actions in GHES 3.14.
However, the warning only appeared after symlinkin node20 to node16. Also note, that the blog post talks about ubuntu16.04 being deprecated but not ubuntu18.04. In reality ubuntu18.04 has the same problem and also causes a crash.

All in all this is a big fail by GitHub not listing all the changes in their release notes. The impact of some of these changes is also not obvious for the normal developer.