Description of problem:
Extended attributes on bricks present even when gluster volume create command fails

Version-Release number of selected component (if applicable):
glusterfs-server-3.7.9-12.el7rhgs.x86_64

How reproducible:
Always

Steps to Reproduce:
1.Create a volume using one correct brick path(/brick1/b1) & 1 wrong brick path(/brick2/b10).
2.gluster volume create command will fail due to wrong brick path
3.Try to run again gluster volume create command with correct brick paths (/brick1/b1) & (/brick2/b2)

Actual results:
gives error for correct brick path in step one bricks like "/brick1/b1 is already part of a volume".

Expected results:
Gluster should roll-back all the xattrs set on bricks if gluster volume create command fails

Additional info:
We can over-ride this issue with use of 'force' in gluster volume create command but that will lead to further consequences by overlooking some other prerequisite,so it doesn't seem to be a good work around.