Bug 987926
| Summary: | ksm is managed by both MOM and ksmtuned on RHEL hosts upgraded from VDSM 3.2 to 3.3 | ||
|---|---|---|---|
| Product: | [Retired] oVirt | Reporter: | Assaf Muller <amuller> |
| Component: | mom | Assignee: | Martin Sivák <msivak> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Barak Dagan <bdagan> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 3.3 | CC: | bdagan, dfediuck, eedri, iheim, msivak, pstehlik |
| Target Milestone: | --- | ||
| Target Release: | 3.3 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | sla | ||
| Fixed In Version: | is9 4.12.0-37.gitfd6a1b7.el6ev.x86_64 | Doc Type: | Bug Fix |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2013-09-23 12:15:03 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: | |||
| Bug Depends On: | |||
| Bug Blocks: | 967562 | ||
|
Description
Assaf Muller
2013-07-24 12:22:27 UTC
*** Bug 987921 has been marked as a duplicate of this bug. *** Running the following commands on host upgraded from 3.2 to 3.3: # service --status-all | grep ksm ksm is not running ksmtuned (pid 8354) is running... # chkconfig | grep ksm ksm 0:off 1:off 2:off 3:on 4:on 5:on 6:off ksmtuned 0:off 1:off 2:off 3:on 4:on 5:on 6:off it seems that the ksmtuned service is not disabled, but ignored. Is this enough ? shouldn't we turned it off + kill it ? ksmtuned is stopped when vdsm starts (http://gerrit.ovirt.org/#/c/17537/). I do not think that "simple" installation of a package should change the global system settings. (In reply to Martin Sivák from comment #3) > ksmtuned is stopped when vdsm starts (http://gerrit.ovirt.org/#/c/17537/). I # service --status-all | egrep -i "ksm|vdsm" ksm is not running ksmtuned (pid 8354) is running... # service vdsmd status VDS daemon server is running > do not think that "simple" installation of a package should change the > global system settings. That is weird. Our vdsm's initscript should stop ksmtuned. But it should not touch ksm at all. Can you: 1) stop vdsm 2) start ksm 3) start ksmtuned 4) start vdsm and check the status after each step? What you describe is quite unusual. ksm should be on at all times. And btw, was vdsm restarted after the upgrade? (In reply to Martin Sivák from comment #5) > That is weird. Our vdsm's initscript should stop ksmtuned. But it should not > touch ksm at all. > > Can you: > 1) stop vdsm # service vdsmd status VDS daemon is not running # service --status-all | egrep 'ksm|ksmtuned' ksm is not running ksmtuned is stopped > 2) start ksm # service vdsmd status VDS daemon is not running # service --status-all | egrep 'ksm|ksmtuned' ksm is running ksmtuned is stopped > 3) start ksmtuned # service vdsmd status VDS daemon is not running # service --status-all | egrep 'ksm|ksmtuned' ksm is running ksmtuned (pid 14894) is running... > 4) start vdsm # service vdsmd status VDS daemon server is running # service --status-all | egrep 'ksm|ksmtuned' ksm is running ksmtuned is stopped > > and check the status after each step? What you describe is quite unusual. > ksm should be on at all times. > > And btw, was vdsm restarted after the upgrade? I'm not sure on what machine I did the verification, but it looks like it did: rose02 ------ 2013-09-04 12:24:40: I am the actual vdsm 4.12.0-105.git0da1561.el6ev 2013-08-28 14:26:07: I am the actual vdsm 4.10.2-24.1.el6ev 2013-08-04 15:10:26: I am the actual vdsm 4.10.2-23.0.el6ev rose03 ------ 2013-09-04 12:26:28: I am the actual vdsm 4.12.0-105.git0da1561.el6ev 2013-08-28 14:25:46: I am the actual vdsm 4.10.2-24.1.el6ev 2013-08-04 14:58:59: I am the actual vdsm 4.10.2-23.0.el6ev Verified on is13 bulk closing, assuming verified bugs are in 3.3. |