Bug 2160660

Summary:	rear mkrescue warning when /usr/lib/firmware link broken
Product:	Red Hat Enterprise Linux 9	Reporter:	tbsky <tbskyd>
Component:	rear	Assignee:	Pavel Cahyna <pcahyna>
Status:	ASSIGNED ---	QA Contact:	CS System Management SST QE <rhel-cs-system-management-subsystem-qe>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	9.1	CC:	pcahyna
Target Milestone:	rc
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:		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 tbsky 2023-01-13 08:02:52 UTC

Hi:
   rhel 9.1 rear 2.6.15 fix broken kernel module links problem https://bugzilla.redhat.com/show_bug.cgi?id=2119501

but there are still similar problems. "linux-firmware" and "microcode_ctl"(when removing old kernel) often cause broken links.

hope "/usr/lib/firmware" can be considered like "/usr/lib/modules" and fixed also.

rhel 9.1 system with package "linux-firmware-20220708-127.el9.noarch" installed result below:

# rear mkrescue
Broken symlink '/usr/lib/firmware/brcm/brcmfmac43455-sdio.AW-CM256SM.txt.xz' in recovery system because 'readlink' cannot determine its link target

Comment 1 Pavel Cahyna 2023-04-03 15:10:43 UTC

Hello tbsky,

thank for your bug report. I would prefer not to add another special case in ReaR. The problem you saw turns out to be just a mistake in the package that contains the firmware file. I reported it as bz2121447 and fixed packages should already be in RHEL 9.2 beta and CentOS 9 Stream. Is that sufficient or do you see another errors of this type? You say "often cause broken links", do you have other examples of broken links?

Best regards, Pavel

Comment 2 tbsky 2023-04-07 03:14:13 UTC

Hi:
   since all broken links are deleted when I saw them, I don't have another example currently. I can only say that the broken links are caused by linux-firmware and microcode_ctl. and these packages won't update for reasons like broken link. so you will see these links always hang there if you don't delete it. I am fine with how Rear works. it is just a little work when Rear complains.