Bug 1257887 - [glusterD]: Brick process is recreated on node where volume is delete and when stopped glusterd is started on other node.
[glusterD]: Brick process is recreated on node where volume is delete and...
Status: CLOSED WONTFIX
Product: Red Hat Gluster Storage
Classification: Red Hat
Component: glusterd (Show other bugs)
3.1
x86_64 Linux
unspecified Severity high
: ---
: ---
Assigned To: Bug Updates Notification Mailing List
Byreddy
: ZStream
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2015-08-28 06:24 EDT by Byreddy
Modified: 2015-08-28 07:24 EDT (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2015-08-28 07:20:40 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Byreddy 2015-08-28 06:24:08 EDT
Description of problem:
Brick process is recreated on node where volume is deleted when stopped glusterd is restarted on other node.

Version-Release number of selected component (if applicable):
glusterfs-3.7.1-13

How reproducible:
always

Steps to Reproduce:
1.Create a Distributed volume using two node cluster (Node-1 and Node-2)
2.Stop glusterd on Node-2 (peer node)
3.Stop and delete the volume on Node-1
4.Start the glusterD on Node-2 and Check the Volume status (gluster v status <vol_name>)
5.Check the volume status on Node-1 also.

Actual results:
Brick process is recreated even after volume delete

Expected results:
Brick process should not recreate after volume delete.

Additional info:

Note You need to log in before you can comment on or make changes to this bug.