Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 2166361

Summary: [RFE]: Check for conflicting versions of languages configured to be used by the user executing the satellite-maintain or satellite-installer command
Product: Red Hat Satellite Reporter: Taft Sanders <tasander>
Component: InstallationAssignee: satellite6-bugs <satellite6-bugs>
Status: CLOSED WONTFIX QA Contact: Satellite QE Team <sat-qe-bz-list>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 6.12.1CC: ehelms
Target Milestone: UnspecifiedKeywords: FutureFeature
Target Release: Unused   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-08-12 23:26:08 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Taft Sanders 2023-02-01 15:22:32 UTC
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.

Comment 1 Eric Helms 2023-03-02 17:13:55 UTC
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.