Description of problem: Currently its just a flag and during sync the enable/disable happens for al the volumes. Also this flag has cluster in unwanted state like if user disabled profiling for few volumes and cluster level flag is set as `enable` it would forcefully again enable for all the volumes. So there is no way to go to a state where it could be mixed state. Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
When one of volumes in cluster is set to Enabled/Disabled when profiling on cluster level is set to Disabled/Enabled then cluster level profiling level is set to Mixed after sync. When cluster level profiling is set to Mixed and profiling on all volumes is set to Enabled/Disabled from cli then profiling on cluster level is set to Enabled/Disabled after sync. --> VERIFIED Tested with: tendrl-ansible-1.6.3-3.el7rhgs.noarch tendrl-api-1.6.3-3.el7rhgs.noarch tendrl-api-httpd-1.6.3-3.el7rhgs.noarch tendrl-commons-1.6.3-4.el7rhgs.noarch tendrl-gluster-integration-1.6.3-2.el7rhgs.noarch tendrl-grafana-plugins-1.6.3-2.el7rhgs.noarch tendrl-grafana-selinux-1.5.4-2.el7rhgs.noarch tendrl-monitoring-integration-1.6.3-2.el7rhgs.noarch tendrl-node-agent-1.6.3-4.el7rhgs.noarch tendrl-notifier-1.6.3-2.el7rhgs.noarch tendrl-selinux-1.5.4-2.el7rhgs.noarch tendrl-ui-1.6.3-1.el7rhgs.noarch
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. https://access.redhat.com/errata/RHSA-2018:2616