Bug 1328836
Summary: | glusterfs-libs postun ldconfig: relative path `1' used to build cache | |||
---|---|---|---|---|
Product: | [Community] GlusterFS | Reporter: | rstory | |
Component: | packaging | Assignee: | Kaleb KEITHLEY <kkeithle> | |
Status: | CLOSED CURRENTRELEASE | QA Contact: | ||
Severity: | low | Docs Contact: | ||
Priority: | unspecified | |||
Version: | 3.7.11 | CC: | bugs, mchangir | |
Target Milestone: | --- | Keywords: | Triaged | |
Target Release: | --- | |||
Hardware: | Unspecified | |||
OS: | Linux | |||
Whiteboard: | ||||
Fixed In Version: | glusterfs-3.7.12 | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | ||
Clone Of: | ||||
: | 1330583 1339610 (view as bug list) | Environment: | ||
Last Closed: | 2016-06-28 12:14:39 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: | ||||
Bug Depends On: | ||||
Bug Blocks: | 1330583, 1331844 |
Description
rstory
2016-04-20 11:53:05 UTC
This was fixed, in Fedora at least, in 3.7.9. It seems there's something different about RHEL or RHEL6. REVIEW: http://review.gluster.org/14082 (packaging: %postun libs ldconfig: relative path `1' used to build cache) posted (#1) for review on release-3.7 by Kaleb KEITHLEY (kkeithle) REVIEW: http://review.gluster.org/14082 (packaging: %postun libs ldconfig: relative path `1' used to build cache) posted (#2) for review on release-3.7 by Kaleb KEITHLEY (kkeithle) COMMIT: http://review.gluster.org/14082 committed in release-3.7 by Kaleb KEITHLEY (kkeithle) ------ commit 6659ff9b81ba0f47e7dd85f947cb8ed5bb41ac26 Author: Kaleb S KEITHLEY <kkeithle> Date: Tue Apr 26 10:33:54 2016 -0400 packaging: %postun libs ldconfig: relative path `1' used to build cache %postun libs isn't 'closed' by the following %postun server on RHEL6 due to the %ifdef...%endif But -server has /usr/lib*/libgfdb.so.x, so we should be running /sbin/ldconfig! Which conveniently fixes the closing issue. See: > Change-Id: Icc365eefc5453c40e02b59288a4e8023b82baa7b > BUG: 1330583 > http://review.gluster.org/14081 Change-Id: I7c2daf1408aaee6340e6983cfaba207c5d13f5a1 BUG: 1328836 Signed-off-by: Kaleb S KEITHLEY <kkeithle> Reviewed-on: http://review.gluster.org/14082 Smoke: Gluster Build System <jenkins.com> CentOS-regression: Gluster Build System <jenkins.com> NetBSD-regression: NetBSD Build System <jenkins.org> REVIEW: http://review.gluster.org/14335 (packaging: %postun libs ldconfig: relative path `1' used to build cache) posted (#1) for review on release-3.7 by Milind Changire (mchangir) REVIEW: http://review.gluster.org/14335 (packaging: %postun libs ldconfig: relative path `1' used to build cache) posted (#2) for review on release-3.7 by Milind Changire (mchangir) Uploading another patch. Moving to POST to get accepted by smoke build. REVIEW: http://review.gluster.org/14335 (packaging: %postun libs ldconfig: relative path `1' used to build cache) posted (#3) for review on release-3.7 by Milind Changire (mchangir) COMMIT: http://review.gluster.org/14335 committed in release-3.7 by Kaleb KEITHLEY (kkeithle) ------ commit 2db5ac501be76bf20f459f0d1440ea6b4ee2d04c Author: Milind Changire <mchangir> Date: Fri May 13 01:12:10 2016 +0530 packaging: %postun libs ldconfig: relative path `1' used to build cache Remove %post{un} {libs|api} -p /sbin/ldconfig optimization and move /sbin/ldconfig on a separate line. Upstream patch: http://review.gluster.org/14312 Change-Id: I8a4c3879afcb7cea08d4b303a2524432d2ffec06 BUG: 1328836 Signed-off-by: Milind Changire <mchangir> Reviewed-on: http://review.gluster.org/14312 Smoke: Gluster Build System <jenkins.com> Reviewed-by: Kaleb KEITHLEY <kkeithle> NetBSD-regression: NetBSD Build System <jenkins.org> CentOS-regression: Gluster Build System <jenkins.com> (cherry picked from commit 84ec13831a4f02cfa8295c9f23b75bf39dc9be30) Reviewed-on: http://review.gluster.org/14335 Tested-by: Kaleb KEITHLEY <kkeithle> This bug is getting closed because a release has been made available that should address the reported issue. In case the problem is still not fixed with glusterfs-3.7.12, please open a new bug report. glusterfs-3.7.12 has been announced on the Gluster mailinglists [1], packages for several distributions should become available in the near future. Keep an eye on the Gluster Users mailinglist [2] and the update infrastructure for your distribution. [1] https://www.gluster.org/pipermail/gluster-devel/2016-June/049918.html [2] http://thread.gmane.org/gmane.comp.file-systems.gluster.user |