changed ubuntu from latest to 22.04

[ckhordiasma]

due to issue https://discourse.ubuntu.com/t/psa-for-folks-using-python-in-github-action-runners-and-ubuntu-latest-label/48654, getting error message:

This environment is externally managed
╰─> To install Python packages system-wide, try apt install
    python3-xyz, where xyz is the package you are trying to
    install.

[jiridanek]

I think better fix is either --break-system-packages, as implemented in skupperproject/skupper-router#1634

or use pipx to install one-off packages if you just run python things, as in red-hat-data-services/ods-ci#1926

edit: or create a venv, possibly with full pyproject.toml and a lock file managed by poetry, and all that, to have the deps versions locked

staying on older ubuntu is unnecessary maintenance debt

edit2: ofc this will work too, I would not mind lgtming what's here, just to unblock things

[ckhordiasma]

@jiridanek Thanks for the feedback, I did some further testing and I found some interesting things: https://github.com/ckhordiasma/rhods-devops-infra/actions/workflows/test.yml

if I use ubuntu-latest, I sometimes get 22.04 and other times get 24.04.

The problem with this is that the pip included in 22.04 does not include the --break-system-packages flag, so half the times the build will fail due to that. Because of this, I am thinking that we should include the --break-system-packages flag and pin the runner to ubuntu-24.04 instead, what do you think?

[ckhordiasma]

actually I am seeing that on my fork it is always using 22.04 if I set the runner to ubuntu-latest. Maybe we can assume that the main repo will stick with using 24.04 when we set the runner to ubuntu-latest, since it has shown a history of using 24.04?

[jiridanek]

Not using ubuntu-latest and specifying a version is a step in the right direction by itself. Whether you'd prefer to start with this PR, set runner version to Ubuntu 22 first, and then make improvements later, or do Ubuntu 24 version from the start, up to you.

The current PR fixes the issue, so wouldn't mind starting with that.

Also, the ubuntu 24 may have some bugs, for example, all runs (that I checked) in this action of mine https://github.com/jiridanek/notebooks/actions/runs/11331224673 are on ubuntu 24, but some of them failed on internal podman error and some passed, seemingly at random.

pip included in 22.04 does not include the --break-system-packages flag

good point, I did not realize that

[ckhordiasma]

ok I'll leave it as-is for now, thanks