Created attachment 1471792 [details] Cluster list Description of problem: When cluster is imported without volumes, cluster level profiling is marked as `unknown` and both options for enable/disable profiling are available. This happens even when user specifies profiling type during importing cluster. Version-Release number of selected component (if applicable): tendrl-ansible-1.6.3-5.el7rhgs.noarch tendrl-api-1.6.3-4.el7rhgs.noarch tendrl-api-httpd-1.6.3-4.el7rhgs.noarch tendrl-commons-1.6.3-9.el7rhgs.noarch tendrl-grafana-plugins-1.6.3-7.el7rhgs.noarch tendrl-grafana-selinux-1.5.4-2.el7rhgs.noarch tendrl-monitoring-integration-1.6.3-7.el7rhgs.noarch tendrl-node-agent-1.6.3-9.el7rhgs.noarch tendrl-notifier-1.6.3-4.el7rhgs.noarch tendrl-selinux-1.5.4-2.el7rhgs.noarch tendrl-ui-1.6.3-8.el7rhgs.noarch How reproducible: 90% Steps to Reproduce: 1. Import cluster without volumes. 2. Set Profiling during import to enabled, disabled or keep current configuration. 3. Go to cluster list when cluster is imported. Actual results: Imported cluster have Volume profiling set to `unknown` in this list and in kebab menu are both options to enable or disable profiling. When one of these options is selected then the cluster level profiling is set correctly. Expected results: Cluster level profiling should have set value that was specified during cluster import. Additional info:
@Filip, in gluster there is nothing like cluster level profiling enabled/disabled. For cluster's ease we have this option provided in WA so that enable/disable can be done for the volumes in the cluster. Regarding `unknown` value for cluster level profiling flag, the cluster level value is actually a derivations based on profiling state for the indidividual volumes. The logic goes as below 1. If all the volumes have profiling enabling - cluster level enabled 2. If all the volumes have profiling disabled - cluster level disabled 3. If few of the volumes have profiling enabled and few disabled - cluster level mixed Now of there are no volumes while importing the cluster, based on what WA should decide the cluster level value? And that's why its marked as `unknown`. Also regarding you saying `Enabled`, `Disable` or `Leave as is` while importing a cluster without volumes, this flag does not have any impact as while first round of syncing the volumes there are no volumes on which this flag should be applied. And that's the reason, both enable/disable options are open post import in WA UI. Based on this marking this BZ as NOT_A_BUG as this is expected behavior.