[Bugs] [Bug 1265633] New: AFR : "gluster volume heal <volume_name info" doesn't report the fqdn of storage nodes.
bugzilla at redhat.com
bugzilla at redhat.com
Wed Sep 23 11:54:34 UTC 2015
https://bugzilla.redhat.com/show_bug.cgi?id=1265633
Bug ID: 1265633
Summary: AFR : "gluster volume heal <volume_name info" doesn't
report the fqdn of storage nodes.
Product: GlusterFS
Version: 3.7.5
Component: replicate
Assignee: bugs at gluster.org
Reporter: ravishankar at redhat.com
CC: bugs at gluster.org, gluster-bugs at redhat.com
Depends On: 1265470
Blocks: 1055968
+++ This bug was initially created as a clone of Bug #1265470 +++
Description of problem:
============================
When a volume is created with bricks containing fully qualified domain names of
the storage nodes, "gluster volume heal <volume_name> info" should also output
fqdn of the storage node like "info healed" and "info split-brain"
Version-Release number of selected component (if applicable):
===============================================================
glusterfs 3.4.0.57rhs built on Jan 13 2014 06:59:05
How reproducible:
===================
Often
Steps to Reproduce:
===================
1. Create a replicated volume with bricks having the fqdn of the storage nodes.
Start the volume.
2. Bring down a brick offline.
3. Create fuse mount. Create few files and directories.
4. Execute "gluster volume heal <volume_name> info"
Actual results:
====================
root at domU-12-31-39-0A-99-B2 [Jan-20-2014- 6:30:51] >gluster v heal importer
info | grep "Brick"
Brick domU-12-31-39-0A-99-B2:/rhs/bricks/importer/
Brick ip-10-82-210-192.ec2.internal:/rhs/bricks/importer
Brick ip-10-234-21-235:/rhs/bricks/importer/
Brick ip-10-2-34-53:/rhs/bricks/importer/
Brick ip-10-114-195-155:/rhs/bricks/importer/
Brick ip-10-159-26-108:/rhs/bricks/importer/
root at domU-12-31-39-0A-99-B2 [Jan-20-2014- 6:29:57] >gluster v heal importer
info healed | grep "Brick"
Brick domU-12-31-39-0A-99-B2.compute-1.internal:/rhs/bricks/importer
Brick ip-10-82-210-192.ec2.internal:/rhs/bricks/importer
Brick ip-10-234-21-235.ec2.internal:/rhs/bricks/importer
Brick ip-10-2-34-53.ec2.internal:/rhs/bricks/importer
Brick ip-10-114-195-155.ec2.internal:/rhs/bricks/importer
Brick ip-10-159-26-108.ec2.internal:/rhs/bricks/importer
root at domU-12-31-39-0A-99-B2 [Jan-20-2014- 6:30:07] >gluster v heal importer
info split-brain | grep "Brick"
Brick domU-12-31-39-0A-99-B2.compute-1.internal:/rhs/bricks/importer
Brick ip-10-82-210-192.ec2.internal:/rhs/bricks/importer
Brick ip-10-234-21-235.ec2.internal:/rhs/bricks/importer
Brick ip-10-2-34-53.ec2.internal:/rhs/bricks/importer
Brick ip-10-114-195-155.ec2.internal:/rhs/bricks/importer
Brick ip-10-159-26-108.ec2.internal:/rhs/bricks/importer
root at domU-12-31-39-0A-99-B2 [Jan-20-2014- 5:36:11] >gluster v info
Volume Name: exporter
Type: Distributed-Replicate
Volume ID: 31e01742-36c4-4fbf-bffb-bc9ae98920a7
Status: Started
Number of Bricks: 2 x 3 = 6
Transport-type: tcp
Bricks:
Brick1: domU-12-31-39-0A-99-B2.compute-1.internal:/rhs/bricks/exporter
Brick2: ip-10-82-210-192.ec2.internal:/rhs/bricks/exporter
Brick3: ip-10-234-21-235.ec2.internal:/rhs/bricks/exporter
Brick4: ip-10-2-34-53.ec2.internal:/rhs/bricks/exporter
Brick5: ip-10-114-195-155.ec2.internal:/rhs/bricks/exporter
Brick6: ip-10-159-26-108.ec2.internal:/rhs/bricks/exporter
Expected results:
====================
"gluster volume heal <volume_name> info" should report the fqdn of the storage
node.
--- Additional comment from Ravishankar N on 2015-09-23 02:31:41 EDT ---
Patch URL: http://review.gluster.org/#/c/12212/
--- Additional comment from Ravishankar N on 2015-09-23 07:51:36 EDT ---
Patch merged. Not sure why bugzilla is not reflecting the status.
Referenced Bugs:
https://bugzilla.redhat.com/show_bug.cgi?id=1055968
[Bug 1055968] AFR : "gluster volume heal <volume_name info" doesn't report
the fqdn of storage nodes.
https://bugzilla.redhat.com/show_bug.cgi?id=1265470
[Bug 1265470] AFR : "gluster volume heal <volume_name info" doesn't report
the fqdn of storage nodes.
--
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.
More information about the Bugs
mailing list