Red Hat Bugzilla – Bug 1316307
Systemd Presets policy do not match preset for lvm2 in RHEL
Last modified: 2017-08-01 13:29:54 EDT
Description of problem: lvm2-lvmpolld.socket is set to forcibly enable in the RPM --scripts for lvm2. However the Red Hat provided systemd preset policy (redhat-release-server) does not match this enforced state (/usr/lib/systemd/system-preset/90-default.preset) Version-Release number of selected component (if applicable): redhat-release-server-7.2-9.el7.x86_64 lvm2-2.02.130-5.el7_2.1.x86_64 How reproducible: Everytime Steps to Reproduce: 1. sudo systemctl status lvm2-lvmpolld.socket Actual results: ● lvm2-lvmpolld.socket - LVM2 poll daemon socket Loaded: loaded (/usr/lib/systemd/system/lvm2-lvmpolld.socket; enabled; vendor preset: disabled) Active: active (listening) since Wed 2016-03-09 15:56:51 AEDT; 17h ago Docs: man:lvmpolld(8) Listen: /run/lvm/lvmpolld.socket (Stream) Expected results: ● lvm2-lvmpolld.socket - LVM2 poll daemon socket Loaded: loaded (/usr/lib/systemd/system/lvm2-lvmpolld.socket; enabled; vendor preset: enabled) Active: active (listening) since Wed 2016-03-09 15:56:51 AEDT; 17h ago Docs: man:lvmpolld(8) Listen: /run/lvm/lvmpolld.socket (Stream) Additional info: rpm -q --scripts lvm2 .... if [ $1 -eq 1 ] ; then # Initial installation systemctl preset lvm2-lvmpolld.socket >/dev/null 2>&1 || : fi # lvm2-lvmpolld socket is always enabled and started and ready to serve if lvmpolld is used # replace direct systemctl calls with systemd rpm macro once this is provided in the macro: # http://cgit.freedesktop.org/systemd/systemd/commit/?id=57ab2eabb8f92fad5239c7d4492e9c6e23ee0678 systemctl enable lvm2-lvmpolld.socket systemctl start lvm2-lvmpolld.socket .... We can work around this by placing in our own preset policy to enable it in /etc/systemd/system-preset/, but Redhat should already provide this policy if it is the default or only use systemctl preset in the RPM.
I agree that we should fix this, adding devel_ack+ Lubos
Updated in redhat-release-{server,client,workstation,computenode}
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2017:1850