'gluster volume status' command produces the error: 'operation failed Failed to get names of volumes'

Solution Verified - Updated -

Issue

  • When one brick has been disconnected from the storage pool, the issuing of the command gluster volume status or gluster volume status all results in the following error:
operation failed
Failed to get names of volumes
  • The gluster peer status command may also incorrectly report that all peers are in a "Connected" state:
# gluster peer status
Number of Peers: 3

Hostname: host1
Uuid: db1182b8-83fb-4d66-8a99-557152b74de2
State: Peer in Cluster (Connected)

Hostname: host2
Uuid: 7bb3b063-ae9e-4397-a829-4f8d7f584e4d
State: Peer in Cluster (Connected)

Hostname: host3
Uuid: 5bb899ed-8c0e-41e8-8977-e2d37e9cada0
State: Peer in Cluster (Connected)

Environment

  • Red Hat Storage 2.0

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content