[Bugs] [Bug 1727682] Upgrade from older versions 3.12.15 and 5.5 to gluster 6.3-1 fails - bricks become offline

bugzilla at redhat.com bugzilla at redhat.com
Mon Jul 8 03:35:12 UTC 2019


https://bugzilla.redhat.com/show_bug.cgi?id=1727682



--- Comment #1 from Amgad <amgad.saleh at nokia.com> ---

How to re-produce:

1) Have a cluster of 3 nodes on 3.12.15
2) Upgraded 1st node to 6.3-1 , bricks on that node went off-line and can't be
brought online till backed out to 3.12.15.
3) If upgrade 2nd node, bricks on that node go offline, etc

The following are the few lines reported in the /var/log/glusterfs/glusterd.log
on the upgraded node

[root at gfs-bcmt-01-control-02 glusterfs]# cat glusterd.log    
[2019-07-08 03:11:18.641072] E [MSGID: 101097]
[xlator.c:218:xlator_volopt_dynload] 0-xlator: dlsym(xlator_api) missing:
/usr/lib64/glusterfs/6.3/rpc-transport/socket.so: undefined symbol: xlator_api
The message "E [MSGID: 101097] [xlator.c:218:xlator_volopt_dynload] 0-xlator:
dlsym(xlator_api) missing: /usr/lib64/glusterfs/6.3/rpc-transport/socket.so:
undefined symbol: xlator_api" repeated 7 times between [2019-07-08
03:11:18.641072] and [2019-07-08 03:11:18.641729]
[2019-07-08 03:31:32.071964] E [MSGID: 101097]
[xlator.c:218:xlator_volopt_dynload] 0-xlator: dlsym(xlator_api) missing:
/usr/lib64/glusterfs/6.3/rpc-transport/socket.so: undefined symbol: xlator_api
The message "E [MSGID: 101097] [xlator.c:218:xlator_volopt_dynload] 0-xlator:
dlsym(xlator_api) missing: /usr/lib64/glusterfs/6.3/rpc-transport/socket.so:
undefined symbol: xlator_api" repeated 7 times between [2019-07-08
03:31:32.071964] and [2019-07-08 03:31:32.072051]
[root at gfs-bcmt-01-control-02 glusterfs]# 


This is really blocking!!!!!!!!!!!!!! Thought release 6.3-1 addressed all the
upgrade issues, not to fail in the first step!!!

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.


More information about the Bugs mailing list