+++ This bug was initially created as a clone of Bug #987293 +++ Description of problem: When an RHS server node is added to a cluster via the Console, the boot-strapping process sets the profile 'virtual-host' for tuned. Before adding the node to a cluster via the Console, the active tuned profile is 'default' Before adding the node: [root@rhs ~]# tuned-adm active Current active profile: default Service tuned: disabled, stopped Service ktune: disabled, stopped After adding the node: [root@rhs ~]# tuned-adm active Current active profile: virtual-host Service tuned: enabled, running Service ktune: enabled, running Version-Release number of selected component (if applicable): Red Hat Storage Console Version: 2.1.0-0.bb8.el6rhs RHS 2.1 : glusterfs-3.4.0.17rhs-1.el6rhs.x86_64 How reproducible: Always Steps to Reproduce: 1.Create a 3.2 compatible cluster via the Console 2.Add a RHS server to the cluster Actual results: Boot-strapping process sets the wrong profile of 'virtual-host' for tuned, when an RHS server node is added to a cluster via the Console. Expected results: Boot-strapping should not set the profile as 'virtual-host' for a RHS node which is added to a cluster. Additional info:
fixed in ovirt-host-deploy-1.1.0-0.8.master.el6ev
Verfied as fixed in ovirt-host-deploy-1.1.0-0.8.master.el6ev.noarch. After bootstrapping - [root@rhs ~]# tuned-adm active │ Current active profile: rhs-virtualization │ Service tuned: enabled, running │ Service ktune: enabled, running
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. http://rhn.redhat.com/errata/RHBA-2013-1262.html