Description
Hi everyone,
Just as info.. also with latest gstatus and gluster 10.1 once inside an replication 1 brick is down > then other Gluster nodes getting an error. even if all is fine (apart of the 1 Brick down). As long the Volume is up > means is not emergency.
may an easy fix?
Traceback (most recent call last):
File "/usr/lib64/python3.6/runpy.py", line 193, in _run_module_as_main
"main", mod_spec)
File "/usr/lib64/python3.6/runpy.py", line 85, in _run_code
exec(code, run_globals)
File "/usr/bin/gstatus/main.py", line 77, in
File "/usr/bin/gstatus/main.py", line 73, in main
File "/usr/bin/gstatus/glusterlib/cluster.py", line 37, in gather_data
File "/usr/bin/gstatus/glustercli/cli/volume.py", line 189, in status_detail
File "/usr/bin/gstatus/glustercli/cli/parsers.py", line 307, in parse_volume_status
AttributeError: 'NoneType' object has no attribute 'get'
thx