+++ This bug was initially created as a clone of Bug #1229202 +++ Description of problem: VDSM service gets killed immediately after start in mom package is not installed. Version-Release number of selected component (if applicable): vdsm-4.17.0-766.git2bf570a.el7.x86_64 How reproducible: Always Steps to Reproduce: 1. Start the VDSM Service by 'service vdsmd start' 2. Check the vdsm service status 'service vdsmd status' Actual results: VDSM service will be in inactive or failed status. Expected results: VDSM service should be running without mom. Additional info: Red Hat Gluster Storage build of VDSM doesn't require MOM as a dependency and vdsmd should run without mom. Also in RHEL-6 VDSM works without mom. --- Additional comment from Red Hat Bugzilla Rules Engine on 2015-06-08 05:19:50 EDT --- This bug is automatically being proposed for Red Hat Gluster Storage 3.1.0 by setting the release flag 'rhgs‑3.1.0' to '?'. If this bug should be proposed for a different release, please manually change the proposed release flag. --- Additional comment from Ramesh N on 2015-06-08 05:20:19 EDT ---
There is a very interesting sequence of actions that is causing this when MOM is not available: 1) systemd starts vdsmd service and makes sure that ksmtuned.service is not running (vdsmd.service contains Conflicts=libvirt-guests.service ksmtuned.service) 2) vdsmd detects that mom is not available and falls back to ksmMonitor (vdsm/ksm.py) 3) ksmMonitor tries to make sure both ksmd and ksmtuned are running (ksm.py:68 and 106) 4) systemd starts preparing ksmtuned start and finds out that vdsmd has a conflict with it 5) ksmtuned's start was requested later than vdsmd and so ksmtuned wins 6) systemd kills vdsmd and starts ksmtuned
Few thoughts here. 1. Are mom and ksmtuned conflicting services? If not, I feel vdsmd can set priority to mom if not available it can do with ksmtunded. 2. I think removing ksmtuned.service from vdsmd.service.in would help as workaround.
1) Yes, those are conflicting. 2) Yes, it does help as a workaround.
I believe right fix would be setting 'conflicts: ksmtuned.service' in mom.service. vdsmd is not the right service for setting conflicts wrt to this.
bug verification steps: Deploy a host, remove mom package using rpm -e --nodeps and restart vdsmd
in 3.5 mom can't be removed from vdsm. in 3.6 mom was separated completely from vdsm. See Bug 1227714.
mistakenly changed.
(In reply to Roy Golan from comment #6) > in 3.5 mom can't be removed from vdsm. in 3.6 mom was separated completely > from vdsm. See Bug 1227714. OK. Not a problem.