[Bugs] [Bug 1511698] Enabling Halo sets volume to Read Only

[bugzilla at redhat.com]

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



--- Comment #3 from Jon Cope <jcope at redhat.com> ---
Here is volume info and status.  I'll attach the logs individually as text.

# gluster volume info

Volume Name: gv0
Type: Replicate
Volume ID: 24831bec-32bb-46a6-9507-6b4c8a8dd14f
Status: Started
Snapshot Count: 0
Number of Bricks: 1 x 4 = 4
Transport-type: tcp
Bricks:
Brick1: gce-node1:/data/brick/gv0
Brick2: gce-node2:/data/brick/gv0
Brick3: gce-node3:/data/brick/gv0
Brick4: gce-node4:/data/brick/gv0
Options Reconfigured:
cluster.halo-enabled: yes
transport.address-family: inet
nfs.disable: on

# gluster volume status
Status of volume: gv0
Gluster process                             TCP Port  RDMA Port  Online  Pid
------------------------------------------------------------------------------
Brick gce-node1:/data/brick/gv0             49152     0          Y       19918
Brick gce-node2:/data/brick/gv0             49152     0          Y       14428
Brick gce-node3:/data/brick/gv0             49152     0          Y       2676
Brick gce-node4:/data/brick/gv0             49152     0          Y       2518
Self-heal Daemon on localhost               N/A       N/A        Y       19939
Self-heal Daemon on gce-node2               N/A       N/A        Y       14449
Self-heal Daemon on gce-node4               N/A       N/A        Y       2539
Self-heal Daemon on gce-node3               N/A       N/A        Y       2697

Task Status of Volume gv0
------------------------------------------------------------------------------
There are no active volume tasks

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