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:

Rebooting a EL7.7 install on a (vmplayer) VM with no LVM devices blocks for ~90 seconds with "A stop job is running for LVM2 metadata daemon"

Version-Release number of selected component (if applicable):

lvm2-2.02.185-2.el7.x86_64
kernel-3.10.0-1062.1.2.el7.x86_64

How reproducible:

Every time

Steps to Reproduce:
1. Install 7.7 on a VM (in this case, not using any LVM devices)
2. Reboot

Actual results:

Shutdown messages stall for 1min 32s with message:

A stop job is running for LVM2 metadata daemon

Expected results:

No wait for LVM2 metadata daemon

Additional info:

Not sure this is because the install has no LVM devices - or for some other reason?

I'd have guessed  related to this upstream commit:

https://www.redhat.com/archives/lvm-devel/2019-September/msg00106.html

We will need a new build with this patch included.

Rebuilding lvm2 with that patch appears to fix the issue for me - thanks

(In reply to Zdenek Kabelac from comment #2)
> I'd have guessed  related to this upstream commit:
> 
> https://www.redhat.com/archives/lvm-devel/2019-September/msg00106.html
> 
> We will need a new build with this patch included.

Gitweb:        https://sourceware.org/git/?p=lvm2.git;a=commitdiff;h=61358d92cbf202dbb483d63a63d5adf0463bb934
Commit:        61358d92cbf202dbb483d63a63d5adf0463bb934
Parent:        5d6bf1efb225b964bfff398277e68345acdac1d0
Author:        Zdenek Kabelac <zkabelac redhat com>
AuthorDate:    Wed Sep 25 17:22:49 2019 +0200
Committer:     Zdenek Kabelac <zkabelac redhat com>
CommitterDate: Mon Sep 30 13:39:44 2019 +0200

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-2020:1129