'gluster peer status' command output doesn't include the peer it is run on
Issue
When running gluster peer status from a node, the output of the command only shows the peer count and peer listing of the other nodes in the cluster, and always excluded the peer it is run from. This causes inconsistent output across nodes and creates problems with scripts.
Environment
- Red Hat Storage Server 2.0
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.
Close
Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.