Could you attach the core file?
This issue is already RCA'd. In the glusterd restore path, if we fail to stop the brick, we fail restore. But the check in the out: section of the function makes a wrong ret check, which causes us to access a NULL new_volinfo thereby causing the crash. Will send the fix for this.
Upstream fix at http://review.gluster.org/9719
Fixed with https://code.engineering.redhat.com/gerrit/42593
Version : glusterfs 126.96.36.199
Retried the steps by making the newly added node not resolve the hostnames of the existing nodes in the cluster and snapshot restore fails as expected. There is no crash seen.
Marking the bug as 'Verified'
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.