2 of the below glusterfsd process cores are being addressed as part of bug1228496 http://pastebin.test.redhat.com/291194 http://pastebin.test.redhat.com/291195 Requesting Pranith/Ravishankar to take a look at the below bt reported and confirm if its a known issue. http://pastebin.test.redhat.com/291198 Rest of the cores look like caused by statedump as you had mentioned or connection loss with brick-process.
As bug1228496 fix is available, request QE to re-run the test and confirm if any of the issues still exist.
M S Vishwanath Bhat helped in running this test once again. There were no crashes reported. For better co-ordination, I am moving QA_Contact for this to him
M S Vishwanath, Could you update the BZ with the recent (re)run of nfs-sanity on a SSL enabled volume?
Moving this BZ to ON_QA with fixed in version as per BZ 1228496, for the following reasons. - There are two sets of crashes that were observed. (Ref: comment #2) BZ 1228496 fixes one of them. The other set of cores doesn't have enough information, see comment #3. - nfs-sanity runs with fix for BZ 1228496 run to completion without crashes. If the cores that weren't analysed due to lack of information in the core reappear, we could open a new BZ tracking only that.
I ran an other job https://bugzilla.redhat.com/show_bug.cgi?id=1233248 and no crashes were found. Moving the bug to verified for now.
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://rhn.redhat.com/errata/RHSA-2015-1495.html