Lock Github workflows to ubuntu-22.04 image

[lunkwill42]

ubuntu-latest has moved to 24.04 and there seems to be problems with running the CI workflows on that version. This locks all workflows to ubuntu-22.04 until we can figure out the issues.

[sonarcloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[github-actions]

🦙 MegaLinter status: ✅ SUCCESS

Descriptor	Linter	Files	Fixed	Errors	Elapsed time

See detailed report in MegaLinter reports
Set VALIDATE_ALL_CODEBASE: true in mega-linter.yml to validate all sources, not only the diff

MegaLinter is graciously provided by

[github-actions]

Test results

    9 files      9 suites   8m 33s ⏱️
2 158 tests 2 158 ✅ 0 💤 0 ❌
4 055 runs  4 055 ✅ 0 💤 0 ❌

Results for commit 45fe42a.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 60.54%. Comparing base (4b527c8) to head (45fe42a).
Report is 2 commits behind head on master.

Additional details and impacted files

@@            Coverage Diff             @@
##           master    #3253      +/-   ##
==========================================
- Coverage   60.55%   60.54%   -0.01%     
==========================================
  Files         606      606              
  Lines       43723    43723              
  Branches       48       48              
==========================================
- Hits        26478    26474       -4     
- Misses      17233    17237       +4     
  Partials       12       12              

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[hmpf]

I'm guessing it's the same stuff that made us lock distro version in argus? That is, system pip behaves very differently now.

[lunkwill42]

I'm guessing it's the same stuff that made us lock distro version in argus? That is, system pip behaves very differently now.

Actually, no.

The problem seems to be the way our Github cache keys are constructed: The same pip cache was re-used when the runner OS was changed - so the workflow began running on Ubuntu 24.04 when GitHub upgraded ubuntu-latest, but the package cache for Ubuntu 22.04 was being re-used. The cache included builds of python-ldap that linked to an older version of libldap.

I was going to make PR for this alternative fix, but I accidentally pushed it directly to master: It seems to have made the test suite run fine again, so I'm opting to close this PR.

Thanks for the review anyway, @hmpf ! :)