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:
Upgrading lvm2 package when lvm snapshots are present triggers lvmetad restart and when lvmetad is starting it gets timed out.
Version-Release number of selected component (if applicable):
lvm2-2.02.176-5.el7.x86_64
How reproducible: Every time
Steps to Reproduce:
1. Install RHEL-7.4 . lvm2 version installed is 2.02.171-8.el7
2. Create an LVM snapshot of rootfs
3. Use RHEL 7.5 ISO to Upgrade lvm2 to RHEL-7.5 version, e.g. lvm2-2.02.176-5.el7.x86_64
Actual results:
$ yum upgrade -y lvm2
Logs:
Feb 09 13:05:32 localhost.localdomain systemd[1]: Reloading.
Feb 09 13:05:32 localhost.localdomain systemd[1]: Stopping LVM2 metadata daemon...
Feb 09 13:05:32 localhost.localdomain lvmetad[490]: Failed to accept connection errno 11.
Feb 09 13:07:02 localhost.localdomain systemd[1]: lvm2-lvmetad.service stop-sigterm timed out. Killing. <==
Feb 09 13:07:02 localhost.localdomain systemd[1]: lvm2-lvmetad.service: main process exited, code=killed, status=9/KILL
Feb 09 13:07:02 localhost.localdomain systemd[1]: Unit lvm2-lvmetad.service entered failed state. <==
Feb 09 13:07:02 localhost.localdomain systemd[1]: lvm2-lvmetad.service failed.
Feb 09 13:07:02 localhost.localdomain systemd[1]: Started LVM2 metadata daemon.
Feb 09 13:07:02 localhost.localdomain systemd[1]: Starting LVM2 metadata daemon...
Feb 09 13:07:02 localhost.localdomain systemd[1]: Reloading.
Feb 09 13:07:03 localhost.localdomain systemd[1]: Started Device-mapper event daemon.
Feb 09 13:07:03 localhost.localdomain systemd[1]: Starting Device-mapper event daemon...
Feb 09 13:07:03 localhost.localdomain dmeventd[1585]: dmeventd ready for processing.
Feb 09 13:07:03 localhost.localdomain lvm[1585]: Monitoring snapshot test-snaplv.
Expected results:
lvmetad should not time-out
Additional info:
No issue observed except for logs reporting lvmetad time-out.