Bug 1782828

Summary:	[RHEL-8.2][RDMA] remove dangling symlink
Product:	Red Hat Enterprise Linux 8	Reporter:	Honggang LI <honli>
Component:	rdma-core	Assignee:	Honggang LI <honli>
Status:	CLOSED ERRATA	QA Contact:	zguo <zguo>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	8.2	CC:	hwkernel-mgr, rdma-dev-team, tmichael, zguo
Target Milestone:	rc
Target Release:	8.2
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	rdma-core-26.0-6.el8	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-04-28 16:57:33 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 Honggang LI 2019-12-12 12:55:35 UTC

Description of problem:

There are some dangling symbolic links should be removed.

https://rpmdiff.engineering.redhat.com/run/425533/27/

NEEDS INSPECTION 	rdma-core-devel 	

File usr/lib64/libefa.so became a dangling symlink (to libefa.so.1) on aarch64 x86_64 ppc64le s390x

	
NEEDS INSPECTION 	rdma-core-devel 	

File usr/lib/libefa.so became a dangling symlink (to libefa.so.1) on i686


NEEDS INSPECTION 	libibverbs 	

File usr/lib64/libibverbs/libefa-rdmav25.so became a dangling symlink (to ../libefa.so.1.1.26.0) on aarch64 x86_64 ppc64le s390x

NEEDS INSPECTION 	libibverbs 	

File usr/lib/libibverbs/libefa-rdmav25.so became a dangling symlink (to ../libefa.so.1.1.26.0) on i686


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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 4 errata-xmlrpc 2020-04-28 16:57:33 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHEA-2020:1865