Bug 764928 (GLUSTER-3196) - ldconfig not run on RPM upgrade
Summary: ldconfig not run on RPM upgrade
Keywords:
Status: CLOSED NOTABUG
Alias: GLUSTER-3196
Product: GlusterFS
Classification: Community
Component: build
Version: 3.2.2
Hardware: x86_64
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Lakshmipathi G
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-07-19 20:53 UTC by Mike Robbert
Modified: 2015-12-01 16:45 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Mike Robbert 2011-07-19 20:53:21 UTC 
I'm not sure why, but it appears the ldconfig is not getting run or at least not working on an RPM upgrade from 3.1.1
I had 3.1.1 installed from an RPM on CentOS 5.4 and today I did a "rpm -U glusterfs*.rpm" with the 3.2.2 RPM files. After that finished I was unable to start glusterd as it was giving the error:

[root@fatcompute-12-1 profile.d]# service glusterd start
Starting glusterd:/opt/glusterfs/3.2.2/sbin/glusterd: error while loading shared libraries: libglusterfs.so.0: cannot open shared object file: No such file or directory
                                                           [FAILED]

I then ran ldconfig and now it starts fine.
Comment 1 Lakshmipathi G 2011-07-26 03:18:34 UTC 
Hi Michael,
Could you please let us, how to reproduce this issue with exact steps ?

I tried following ,but it (unfortunately :P)  worked.

1)started with clean setup
#whereis gluster glusterfs glusterd glusterfsd
gluster:
glusterfs:
glusterd:
glusterfsd:

# ls
glusterfs-core-3.1.1-1.fc11.x86_64.rpm  glusterfs-core-3.2.2-1.fc12.x86_64.rpm

2)installed 3.1.1 rpm
# rpm -ivh glusterfs-core-3.1.1-1.fc11.x86_64.rpm 
Preparing...                ########################################### [100%]
   1:glusterfs-core         ########################################### [100%]

3)Version check-

# glusterd --version
glusterfs 3.1.1 built on Nov 30 2010 04:06:40
Repository revision: v3.1.1
Copyright (c) 2006-2010 Gluster Inc. <http://www.gluster.com>
GlusterFS comes with ABSOLUTELY NO WARRANTY.
You may redistribute copies of GlusterFS under the terms of the GNU Affero General Public License.

4)Now upgrade to 3.2.2

# rpm -Uvh glusterfs-core-3.2.2-1.fc12.x86_64.rpm 
Preparing...                ########################################### [100%]
   1:glusterfs-core         ########################################### [100%]
[root@space rpm]# glusterd --version
glusterfs 3.2.2 built on Jul 14 2011 19:27:18
Repository revision: git://git.gluster.com/glusterfs.git
Copyright (c) 2006-2010 Gluster Inc. <http://www.gluster.com>
GlusterFS comes with ABSOLUTELY NO WARRANTY.
You may redistribute copies of GlusterFS under the terms of the GNU Affero General Public License.

For me upgrade(from 3.1.1. to 3.2.2) works without manually invoking ldconfig.
Comment 2 Lakshmipathi G 2011-09-16 07:35:08 UTC 
Unable to reproduce this again.Please re-open ,if the issue still exists.
Note You need to log in before you can comment on or make changes to this bug.