Bug 2189355

Summary:	[HPE 9.3 Bug] libxcrypt-compat inconsistently installed.
Product:	Red Hat Enterprise Linux 9	Reporter:	Jerry Hoemann <jerry.hoemann>
Component:	libxcrypt	Assignee:	Stanislav Zidek <szidek>
Status:	CLOSED NOTABUG	QA Contact:	BaseOS QE Security Team <qe-baseos-security>
Severity:	high	Docs Contact:
Priority:	medium
Version:	9.3	CC:	bfinger, fweimer, jerry.hoemann, jkachuck, joseph.szczypek, jwboyer, karen.skweres, mknutson, trinh.dao
Target Milestone:	rc	Keywords:	Triaged
Target Release:	---
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.