Bug 987921 - Upgrading a RHEL host from VDSM 3.2 to 3.3 does not disable ksmtuned, but MOM makes calls to ksm as well
Summary: Upgrading a RHEL host from VDSM 3.2 to 3.3 does not disable ksmtuned, but MOM...
Keywords:
Status: CLOSED DUPLICATE of bug 987926
Alias: None
Product: oVirt
Classification: Retired
Component: mom
Version: 3.3
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: Adam Litke
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-07-24 12:20 UTC by Assaf Muller
Modified: 2013-07-24 12:23 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-07-24 12:23:46 UTC
oVirt Team: ---
Embargoed:

Attachments (Terms of Use)

Description Assaf Muller 2013-07-24 12:20:09 UTC 
Description of problem:
In 3.2 VDSM talked to ksm via ksmtuned. 3.3 VDSM uses MOM to talk to ksm, but upgrading VDSM from 3.2 to 3.3 doesn't disable ksmtuned. That means that VDSM may send conflicting instructions to KSM as both ksmtuned and MOM are active. In systemd we marked VDSM as conflicting with ksmtuned, so something similar needs to happen with systemV.

Additionally, there is a nontrivial amount of code in VDSM with the 

Version-Release number of selected component (if applicable):
oVirt Engine Version: 3.3.0-0.3.beta1.fc19
VDSM 4.12.0-0.1.rc3
Comment 1 Assaf Muller 2013-07-24 12:23:46 UTC 

*** This bug has been marked as a duplicate of bug 987926 ***
Note You need to log in before you can comment on or make changes to this bug.