Bug 1259288
| Summary: | [RHEVM-RHGS] RHGS bootstrapping invokes with older RHGS tuned profile name | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Virtualization Manager | Reporter: | SATHEESARAN <sasundar> |
| Component: | ovirt-engine | Assignee: | Sahina Bose <sabose> |
| Status: | CLOSED ERRATA | QA Contact: | SATHEESARAN <sasundar> |
| Severity: | high | Docs Contact: | |
| Priority: | medium | ||
| Version: | 3.5.4 | CC: | amainkar, bgraveno, bmcclain, gklein, lsurette, maurizio.antillon, rbalakri, rcyriac, Rhev-m-bugs, sabose, sasundar, srevivo, ykaul |
| Target Milestone: | ovirt-4.0.0-rc | ||
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: |
Previously, new tuned profiles that were introduced in Red Hat Enterprise Linux 7 for Red Hat Gluster Storage was not available in the Red Hat Gluster Storage Console. As a consequence, users were unable to set the tuned profile from console. With this update, users can select cluster specific profiles using console.
|
Story Points: | --- |
| Clone Of: | Environment: |
RHGS 3.1
|
|
| Last Closed: | 2016-08-23 20:28:50 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | Gluster | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | |||
| Bug Blocks: | 1249979 | ||
Refer this bug for RHSC - https://bugzilla.redhat.com/show_bug.cgi?id=1242902 Need to backport tuned profile related patches to 3.6. Added RHGS 3.1.2 node to 3.5 cluster. While creating the cluster chosen the tuned-profile as "rhs-virtualization", but still I see the error "Unable to set tuned profile" in logs As I get the information from Sahina, it looks like this bug can't be verified for RHEV 3.6.5 as RHGS 3.1.2 or RHGS 3.1.3 couldn't be managed by RHEV 3.6 in 3.6 cluster. @Sahina, what should be the ideal state this bug should be in ? With RHGS 3.1.x - the nodes can only be added to a 3.5 cluster and the new tuned profiles are only supported from 3.6 cluster. Bronce, This bug couldn't be verified for RHEV 3.6.6 too as because of the reason mentioned in comment6 Probably this bug needs to be moved to the RHEV release, when RHGS ships the compatible vdsm ( 4.17.* ), so that RHGS node can be added to RHEV 3.6 cluster (In reply to SATHEESARAN from comment #7) > Bronce, > > This bug couldn't be verified for RHEV 3.6.6 too as because of the reason > mentioned in comment6 > > Probably this bug needs to be moved to the RHEV release, when RHGS ships the > compatible vdsm ( 4.17.* ), so that RHGS node can be added to RHEV 3.6 > cluster Do we know when that version of vdsm will be included in RHGS? I'll re-target this to RHEV 3.6.7 for now as that will be the next release on 22-June. (In reply to Bronce McClain from comment #8) > Do we know when that version of vdsm will be included in RHGS? I'll > re-target this to RHEV 3.6.7 for now as that will be the next release on > 22-June. Bronce I don't have that information Sahina, Do we have the information required by Bronce in comment8 ? RHGS 3.1.x has 4.16.* versions - which cannot be added to 3.6 clusters. This bug will need to wait for an RHGS 3.2 I will retarget to 4.0 Tested with RHGS 3.1.3 ( with vdsm 4.17.33-1 ) and RHV 4.0.2-6 by adding this node to the 3.6 cluster. The gluster cluster is created with tuned-profile set to rhgs-random and the newly added nodes has this profile set 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://rhn.redhat.com/errata/RHEA-2016-1743.html |
Description of problem: ----------------------- With RHGS 3.1 , tuned-profiles for RHGS are renamed as 'rhgs-sequential-io' Version-Release number of selected component (if applicable): ------------------------------------------------------------- RHGS 3.1 RHEV 3.5.3 How reproducible: ----------------- Always Steps to Reproduce: ------------------- 1. Add RHGS node in gluster-service enabled cluster Actual results: --------------- Errors seen while setting tuned profile named 'rhs-virtualization' Expected results: ----------------- New rhgs tuned profile 'rhgs-sequential-io' should be set instead of 'rhs-virtualization' Additional Info: ----------------- Error messages as seen ovirt host deploy logs <snip> 2015-09-02 03:46:01 DEBUG otopi.plugins.ovirt_host_deploy.tune.tuned plugin.executeRaw:824 execute: ('/sbin/tuned-adm', 'profile', 'rhs-virtualization'), executable='None', cwd='None', env=None 2015-09-02 03:46:51 DEBUG otopi.plugins.ovirt_host_deploy.tune.tuned plugin.executeRaw:874 execute-result: ('/sbin/tuned-adm', 'profile', 'rhs-virtualization'), rc=1 2015-09-02 03:46:51 DEBUG otopi.plugins.ovirt_host_deploy.tune.tuned plugin.execute:932 execute-output: ('/sbin/tuned-adm', 'profile', 'rhs-virtualization') stdout: 2015-09-02 03:46:51 DEBUG otopi.plugins.ovirt_host_deploy.tune.tuned plugin.execute:937 execute-output: ('/sbin/tuned-adm', 'profile', 'rhs-virtualization') stderr: 2015-09-02 03:46:26,610 ERROR dbus.proxies: Introspect error on :1.2:/Tuned: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. ERROR:dbus.proxies:Introspect error on :1.2:/Tuned: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. DBus call to Tuned daemon failed Requested profile 'rhs-virtualization' doesn't exist. 2015-09-02 03:46:51 WARNING otopi.plugins.ovirt_host_deploy.tune.tuned tuned._misc:91 Cannot set tuned profile 2015-09-02 03:46:51 DEBUG otopi.context context._executeMethod:138 Stage misc METHOD otopi.plugins.ovirt_host_deploy.vdsm.bridge.Plugin._misc 2015-09-02 03:46:51 DEBUG otopi.context context._executeMethod:144 condition False </snip>