Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 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 "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". 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 "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-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 2189355

Summary: [HPE 9.3 Bug] libxcrypt-compat inconsistently installed.
Product: Red Hat Enterprise Linux 9 Reporter: Jerry Hoemann <jerry.hoemann>
Component: libxcryptAssignee: Stanislav Zidek <szidek>
Status: CLOSED NOTABUG QA Contact: BaseOS QE Security Team <qe-baseos-security>
Severity: high Docs Contact:
Priority: medium    
Version: 9.3CC: bfinger, fweimer, jerry.hoemann, jkachuck, joseph.szczypek, jwboyer, karen.skweres, mknutson, trinh.dao
Target Milestone: rcKeywords: Triaged
Target Release: ---Flags: pm-rhel: mirror+
Hardware: aarch64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-05-03 09:30:45 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 Jerry Hoemann 2023-04-24 23:16:38 UTC
Description of problem:

libxcrypt-compat is not being installed on Rhel 9.3 aarch64 where it is being installed with Rhel 9.3 x86_64.

I would have thought that the same set of libraries (sans architecture specific ones) would be installed for both x86 and aarch64.

I noticed the issue as the hpe ilorest command links against /usr/lib64/libcrypt.so.1 which is delivered as part of libxcrypt-comat.

From Bug #2034569, it appears that Rhel wants to deprecate this library for RHEL 10, but shouldn't it still be in Rhel 9.x?

I believe this issue exists on Rhel 9.2 as well.

Version-Release number of selected component (if applicable):
RHEL-9.3.0-20230417.0


How reproducible:


Steps to Reproduce:
1.Cold install from ISO
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Stanislav Zidek 2023-04-26 12:41:47 UTC
Hello, thanks for filing the bug. I confirm the behaviour you are describing. This is most probably not an issue in `libxcrypt` component though, so I filed a general CentOS Stream 9 request: https://issues.redhat.com/browse/CS-1572 Let's discuss it there if needed, I'll close this bug once it's confirmed it is not libxcrypt problem.

Comment 5 Stanislav Zidek 2023-05-03 09:30:45 UTC
After internal discussion, we decided that it is less desirable to bloat default installation with additional packages (than keeping default installation on various architectures consistent). "Workaround" should be pretty simple though, just make `libxcrypt-compat` an explicit dependency of the tool in question. I am using quotes because it is not really a workaround, just the correct thing to do anyway.