Improve python version flexibility

[dralley]

• Changes the default CI image to centos9
  • Before merging let's make sure the older branches we care about have already had their template configs updated to specify the old image. pulpcore, pulp_rpm are already done, pulp_container has PRs up, not sure about the rest
• Fixes hardcoded references to Python 3.8 in the template

[noissue]

[dralley]

Note: none of these are in the template, it's the CI for the template itself

[dralley]

@gerrod3 Looking at the test failure.. this line of code doesn't even exist in recent versions, we replaced aiohttp a full year ago

https://github.com/pulp/plugin_template/actions/runs/7911045981/job/21594626348?pr=845#step:15:133

https://github.com/pulp/pulpcore/pull/3575/files

Any idea how this would be happening?

[mdellweg]

One nitpick, but also not a thing i want to hold off for.
Let's get this forward with!

[gerrod3]

@gerrod3 Looking at the test failure.. this line of code doesn't even exist in recent versions, we replaced aiohttp a full year ago

https://github.com/pulp/plugin_template/actions/runs/7911045981/job/21594626348?pr=845#step:15:133

https://github.com/pulp/pulpcore/pull/3575/files

Any idea how this would be happening?

We need to update this bootstrap line: https://github.com/pulp/plugin_template/blob/main/templates/bootstrap/requirements.txt#L1
CatDog is getting bootstrapped with a super old version of pulpcore that uses old requirements that are not compatible with python 3.11

[dralley]

@gerrod3 @mdellweg If we want to keep the older branches of various plugins using the older CI images, and I assume we do if our goal is maximal stability, then we need to do a round of CI updates to set the ci_base_image template var on all of the old branches.

The easiest way to do that is trigger the action right now prior to merging this PR, as it will fill out the default automatically. This is already done for pulpcore, pulp_rpm, and pulp_container but it doesn't look like ansible or gem are updated (beyond the main branch), and I don't have permissions to trigger the actions in those repos.

[gerrod3]

The easiest way to do that is trigger the action right now prior to merging this PR, as it will fill out the default automatically. This is already done for pulpcore, pulp_rpm, and pulp_container but it doesn't look like ansible or gem are updated (beyond the main branch), and I don't have permissions to trigger the actions in those repos.

pulp_gem and pulp_ansible have been updated. We still need to update pulp_ostree and pulp_deb. And do we need to do anything for pulp_file?

[dralley]

pulp_file no longer has independent CI, so no.

[mdellweg]

pulp_file no longer has independent CI, so no.

Stable branches do...

[dralley]

That's true