Description of problem: ----------------------- With hyperconverged setup, self-hosted engine is used. As part of Hosted engine deployment, HE VM was brought up with the first host added to the 'default' cluster. When editing the cluster, after selecting 'Enable Gluster Service', the 'Gluster Tuned Profile' tab is grayed out Version-Release number of selected component (if applicable): ------------------------------------------------------------- oVirt-4.1 How reproducible: ----------------- Always Steps to Reproduce: ------------------- 1. Post self-hosted engine deployment, edit the cluster to enable gluster service and with tuned profile Actual results: --------------- Tuned profile drop-down list is grayed out Expected results: ----------------- There should be a way to set the required tuned profile on the cluster, when one of the host is already available in the cluster
Created attachment 1235592 [details] screenshot showing edit cluster dialog
Setting of the tuned profile is possible only when hosts are not added to the cluster as the profile is set while installing the host.
Sas, for HC clusters, "virtual-host" profile is set by default, if no profile is chosen. Is this still a high sev bug given this?
(In reply to Sahina Bose from comment #3) > Sas, for HC clusters, "virtual-host" profile is set by default, if no > profile is chosen. > > Is this still a high sev bug given this? The only concern here is that when there are new profiles to cater different needs of the stack - say profile for certain workload - then we don't have a way to change or modify the tuned profile from RHV UI
The issue with allowing edit of tuned profile for cluster with existing hosts - the tuned profile is only set during installation of the host. We will not know if tuned profile that's selected in cluster is applied to host or not. So there are multiple issues to solve here: 1. Display the currently applied tuned profile in the Hosts General sub-tab 2. Allow for setting the tuned profile after installation of host as well, maybe during activation of host. Since this is not a high priority issue, moving to 4.2
*** This bug has been marked as a duplicate of bug 1588932 ***