This happens if get-state from gluster doesn't report volume specific profiling enabled value. In this case volume level values for profiling_enabled flag would be set as Unknown and so at cluster level we should not set the value of cluster.profiling_enabled_state. Later if user enables/disables profiling from UI the respective value should be set for cluster volume still would report as Unknown because get-state doesnt support the details.
This whole thing is required only for a glusterfs version which doesn't report profiling information at individual volume level.
This happens if get-state from gluster doesn't report volume specific profiling enabled value. In this case volume level values for profiling_enabled flag would be set as Unknown and so at cluster level we should not set the value of cluster.profiling_enabled_state. Later if user enables/disables profiling from UI the respective value should be set for cluster volume still would report as Unknown because get-state doesnt support the details.
This whole thing is required only for a glusterfs version which doesn't report profiling information at individual volume level.