Bug 1510735

Summary: Missing symbols in regression core
Product: [Community] GlusterFS Reporter: Nigel Babu <nigelb>
Component: project-infrastructureAssignee: Nigel Babu <nigelb>
Status: CLOSED CURRENTRELEASE QA Contact:
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: mainlineCC: bugs, gluster-infra
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: glusterfs-4.1.3 (or later) Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-08-29 03:36:14 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:

Description Nigel Babu 2017-11-08 06:30:39 UTC
Pasting in Shyam's analysis so we can fix it:

> Problem is due to (2) below, but (1) also needs addressing I think.
>       
> Failed regression that Nigel pointed me to: https://build.gluster.org/job/regression-test-with-multiplex/438/console
> 
> 2 bugs:
> 1) this line https://github.com/gluster/glusterfs-patch-acceptance-tests/blob/master/regression.sh#L27 should have "set pagination off" as follows,
> 
> gdb -c <path to core> -q -ex "set pagination off" -ex "info sharedlibrary" -ex q 2>/dev/null
> 
> 2) this line https://github.com/gluster/glusterfs-patch-acceptance-tests/blob/master/regression.sh#L109 can be changed to:
> 
> gdb -ex 'core-file <path to core>' -ex 'set pagination off' -ex 'info proc exe' -ex q 2>/dev/null | tail -1
> 
> Alternative to the above would be to extract the executable name from,
file <corefile>, but I am not certain the output would be similar on all systems.

Comment 1 Nigel Babu 2017-11-13 05:05:08 UTC
Pushed a patch to fix this based on Shyam's suggestion: https://github.com/gluster/glusterfs-patch-acceptance-tests/pull/103

Comment 2 Amar Tumballi 2018-08-29 03:36:14 UTC
This update is done in bulk based on the state of the patch and the time since last activity. If the issue is still seen, please reopen the bug.