[Bugs] [Bug 1402688] "gluster get-state" is capturing the port number for the stopped state brick process.

[bugzilla at redhat.com]

https://bugzilla.redhat.com/show_bug.cgi?id=1402688



--- Comment #1 from Atin Mukherjee <amukherj at redhat.com> ---
Description of problem:
=======================
"gluster get-state" is capturing the port number for the stopped state brick
process.

Volume1.Brick1.path: 10.70.41.198:/bricks/brick0/q0
Volume1.Brick1.hostname: 10.70.41.198
Volume1.Brick1.port: 49152         <==========
Volume1.Brick1.rdma_port: 0
Volume1.Brick1.status: Stopped   <===========
Volume1.Brick1.signedin: False
Volume1.Brick2.path: 10.70.41.217:/bricks/brick0/q1
Volume1.Brick2.hostname: 10.70.41.217
Volume1.Brick3.path: 10.70.41.198:/bricks/brick1/q2
Volume1.Brick3.hostname: 10.70.41.198
Volume1.Brick3.port: 49153
Volume1.Brick3.rdma_port: 0
Volume1.Brick3.status: Stopped
Volume1.Brick3.signedin: False
Volume1.Brick4.path: 10.70.41.217:/bricks/brick1/q3
Volume1.Brick4.hostname: 10.70.41.217 


Actual results:
===============
"gluster get-state" is capturing the port number for the stopped state brick
process.

Expected results:
=================
port should be 0

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.