Description of problem:
There is no information about profiling enabled/not-started at volume level in get-state output
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Setup a gluster cluster with 3 nodes
2. Create a dist-replicate volume
3. Start volume profile on the volume
4. Run the command `gluster get-state` and check the output
There is not detail of volume profiling enaled
The get-state output should mention if volume profiling is enabled/not-started for the volume
upstream patch : https://review.gluster.org/#/c/19286
Build : 3.12.2-5
Profile enabled option is present in the recent gluster get-state
<Snippet from get-state>
Hence marking it as verified
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.