CentOS Stream 9 - platform python (3.9) and netbox required python (>3.10) : system conflict #18342
Replies: 3 comments
-
Does this instruction solve your problem: https://netboxlabs.com/docs/netbox/en/stable/installation/3-netbox/#run-the-upgrade-script
Also general note that Python 3.9 will be end-of-life this year: https://devguide.python.org/versions/ |
Beta Was this translation helpful? Give feedback.
-
Hi, I will test that on our reference machine (I've to reset the setup) I'll let you know the result (As for Python 3.9 EoL ... I know... but it sometimes takes much longer before it is replaced as "platform python" in CentOS .. .we'll see how that goes. ) |
Beta Was this translation helpful? Give feedback.
-
So that works nicely, so far no issues with either Netbox or the OS. |
Beta Was this translation helpful? Give feedback.
-
Hi,
I'm not sure this is the right place, but I hope I can get some advice.
I've to use a CentOS Stream 9 provided image (which also uses cloud-init).
On CentOS (like on RH) the system or platform python version is 3.9, whereas Netbox requires >3.10
I installed python3.12 (and python3.12-devel). After the installation I used
to add python 3.12 as alternative with priority 2 and then switch the default to python3.12
I assumed that the OS would continue to use the platform python, but that does not seem to be the case, or I set it up the wrong way.
However, after this, there is a lot of things breaking on the OS level (cloud-init, firewalld, ....)
It seems that for some reason, there is a lot of python modules (required by the OS) which are not (no longer) available for python 3.12?
For example cloud-init:
when running with python 3.9,
when running under python 3.12
I noticed python 3.9 was not in the list of alternatives, so I added it (with priority 1).
and switched back to python 3.9
after this, the system/os are no longer broken, but of course then it no longer works for netbox
I trying to fix python 3.12 to make it run as platform python is probably a bad idea (or will not work).
Did I make a mistake with setting up with alternatives?
Anyone some advice or tips on how I can solve this? --> ensure that the os keeps using python3.9 while users default to python3.12.
If that is really impossible, how can I ensure that Netbox always uses python 3.12 (for example for the upgrade script, running netbox, netbox scripts, etc...) while the system default is python 3.9?
I appreciate any help
Thanks,
Beta Was this translation helpful? Give feedback.
All reactions