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 1700685 - /sbin/ldconfig: relative path `1' used to build cache
Summary: /sbin/ldconfig: relative path `1' used to build cache
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: anaconda
Version: 8.0
Hardware: Unspecified
OS: Unspecified
high
medium
Target Milestone: rc
: 8.0
Assignee: Jiri Konecny
QA Contact: Release Test Team
URL:
Whiteboard:
Depends On:
Blocks: 1755139
TreeView+ depends on / blocked
 
Reported: 2019-04-17 07:39 UTC by Alexander Todorov
Modified: 2020-04-28 15:31 UTC (History)
5 users (show)

Fixed In Version: anaconda-29.19.2.2-1
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-04-28 15:30:46 UTC
Type: Bug
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2020:1584 0 None None None 2020-04-28 15:31:18 UTC

Description Alexander Todorov 2019-04-17 07:39:33 UTC
Description of problem:

Output from RPM Command:
/sbin/ldconfig: relative path `1' used to build cache
warning: %postun(anaconda-widgets-29.19.0.39-1.el8.s390x) scriptlet failed, exit status 1

Seeing this on aarch64 and s390x for 0day advisories TPS

Comment 2 Jan Stodola 2019-07-04 12:34:12 UTC
Reproducer:
erase or update anaconda-widgets on s390x/aarch64:

# yum erase anaconda-widgets
...
  Erasing          : anaconda-widgets-29.19.0.40-1.el8.s390x                          1/4 
  Running scriptlet: anaconda-widgets-29.19.0.40-1.el8.s390x                          1/4 
/sbin/ldconfig: relative path `0' used to build cache
warning: %postun(anaconda-widgets-29.19.0.40-1.el8.s390x) scriptlet failed, exit status 1

Error in POSTUN scriptlet in rpm package anaconda-widgets


# yum update anaconda-widgets
...
  Upgrading        : anaconda-widgets-29.19.1.6-1.el8.s390x                           1/2 
  Running scriptlet: anaconda-widgets-29.19.1.6-1.el8.s390x                           1/2 
  Cleanup          : anaconda-widgets-29.19.0.40-1.el8.s390x                          2/2 
  Running scriptlet: anaconda-widgets-29.19.0.40-1.el8.s390x                          2/2 
/sbin/ldconfig: relative path `1' used to build cache
warning: %postun(anaconda-widgets-29.19.0.40-1.el8.s390x) scriptlet failed, exit status 1

Error in POSTUN scriptlet in rpm package anaconda-widgets

Comment 4 Jiri Konecny 2019-10-08 11:39:56 UTC
PR: https://github.com/rhinstaller/anaconda/pull/2167

Comment 9 Zdenek Veleba 2020-02-03 15:14:26 UTC
Verified

Comment 11 errata-xmlrpc 2020-04-28 15:30:46 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/RHBA-2020:1584


Note You need to log in before you can comment on or make changes to this bug.