Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 987921

Summary:	Upgrading a RHEL host from VDSM 3.2 to 3.3 does not disable ksmtuned, but MOM makes calls to ksm as well
Product:	[Retired] oVirt	Reporter:	Assaf Muller <amuller>
Component:	mom	Assignee:	Adam Litke <alitke>
Status:	CLOSED DUPLICATE	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	3.3	CC:	dfediuck, iheim
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-07-24 12:23:46 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

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 ***