Description of problem: Satellite-installer should detect if the user used to invoke the command has a custom language path configured for the necessary languages needed by Satellite. Version-Release number of selected component (if applicable): n/a How reproducible: n/a Steps to Reproduce: 1. 2. 3. Actual results: Installer fails with very unique errors when custom languages are configured on the host. Expected results: Step 1 of the installer should be to validate or set the path of the language used by a user for the entirety of the run of the command. Additional info: A simple example with a custom python environment: [root@bombsat610 ~]# ll /usr/local/lib/ total 21352 -r-xr-xr-x. 1 root root 21848784 Aug 25 07:44 libpython3.6m.a drwxr-xr-x. 2 root root 27 Aug 25 07:45 pkgconfig drwxr-xr-x. 35 root root 8192 Aug 25 07:44 python3.6 Satellite upgrade fails with the following: 2023-02-01 07:21:03 [ERROR ] [configure] 'pulpcore-manager migrate --noinput' returned 1 instead of one of [0] 2023-02-01 07:21:03 [ERROR ] [configure] /Stage[main]/Pulpcore::Database/Pulpcore::Admin[migrate --noinput]/Exec[pulpcore-manager migrate --noinput]/returns: change from 'notrun' to ['0'] failed: 'pulpcore-manager migrate --noinput' returned 1 instead of one of [0] Removing this custom python version from this path allowed the upgrade to use the correct python and access the correct libraries. A check for alternate language binaries should be checked for at the start of an installer run.
I don't think we are likely to address this issue. We expect the system to be a clean RHEL installation and for things like other Python's not to exist outside of what is required by Satellite.