Bug 987077
Summary: | [RHEV+RHS] - Step for setting profile for tuned fails during boot-strapping, when adding RHS2.0Update5 to RHEVM 3.2 Gluster Enabled Cluster, with Compatibility version set to 3.1 | ||
---|---|---|---|
Product: | [oVirt] ovirt-host-deploy | Reporter: | Rejy M Cyriac <rcyriac> |
Component: | Plugins.tune | Assignee: | Alon Bar-Lev <alonbl> |
Status: | CLOSED DUPLICATE | QA Contact: | Haim <hateya> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 1.0.0 | CC: | acathrow, alonbl, barumuga, bazulay, dougsland, ecohen, grajaiya, iheim, Rhev-m-bugs, sabose, yeylon |
Target Milestone: | --- | Keywords: | Triaged |
Target Release: | --- | Flags: | pm-rhel:
devel_ack?
|
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | gluster | ||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: |
virt rhev integration
|
|
Last Closed: | 2013-08-19 06:47:13 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: |
Description
Rejy M Cyriac
2013-07-22 16:22:29 UTC
I reduced the error to warning as older rhel do not support the virtual-host profile. So it has nothing to do with the compatibility level, but the actual distribution. (In reply to Alon Bar-Lev from comment #1) > I reduced the error to warning as older rhel do not support the virtual-host > profile. So it has nothing to do with the compatibility level, but the > actual distribution. It appears that the profile being attempted to be set for tuned, on the RHS server node, is itself wrong. The profile to be set for tuned, on RHS server added to Gluster Enabled Cluster, should be 'rhs-virtualization'. This profile is available on RHS 2.0 Update 5 and RHS 2.1 . Opened BZ 987293 for that. Fix of that BZ should resolve this one. - rejy (rmc) Why don't you mark bugs as duplicate, when have the same cause? More correctly why do you open new bugs? I think this one is for RHS 2.0 with different compatibility version 3.1. You could close as duplicate if this is not needed. (In reply to Bala.FA from comment #5) > I think this one is for RHS 2.0 with different compatibility version 3.1. > You could close as duplicate if this is not needed. I don't know if it is needed or not as I am not familiar with your build scheme. However, usually there should be one bug to fix an issue, the cloned once to each past versions if required to fix at these as well. So I mark it as duplicate then you can clone the other bug. BUT: having a separate bug opened and state that this bug can be closed when the other bug is resolved, probably not good idea. *** This bug has been marked as a duplicate of bug 987293 *** |