Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
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.
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
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.