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.

lvmetad is now enabled in el7 builds. Seems the patch did not made it into dracut.el7 as suggested by following in the rdsosreport.txt attached to Bug 994978:

    /usr/sbin/rdsosreport@35(): command -v lvm
    /usr/sbin/rdsosreport@36(): lvm pvdisplay
      /run/lvm/lvmetad.socket: connect failed: No such file or directory
      WARNING: Failed to connect to lvmetad: No such file or directory. Falling back to internal scanning.
      /run/lvm/lvmetad.socket: connect failed: No such file or directory
    ...

+++ This bug was initially created as a clone of Bug #811129 +++

Currently dracut uses lvm.conf as found in the system and modifies only global/locking_type setting. As there's a new feature introduced - the lvmetad daemon, dracut should disable its use as well by setting "global/use_lvmetad=0"
(patch attached).

Otherwise, there's a warning message issued:

dracut: WARNING: Failed to connect to lvmetad: No such file or directory. Falling back to internal scanning.

commit 69f7ed96109095c8d3c39c1f741598119b602936

dracut-032-1.el7

Please test http://people.redhat.com/harald/downloads/dracut/dracut-033-67.el7/ if possible

Verified on RHEL-7.0-20140210.0 with dracut-033-115.el7.

[root@rhevh-x3650-01-g7 ~]#  lsinitrd -f /etc/lvm/lvm.conf | grep use_lvmetad
    # lvmetad is used" comment that is attached to global/use_lvmetad setting.
    # supported in clustered environment. If use_lvmetad=1 and locking_type=3
    # If lvmetad has been running while use_lvmetad was 0, it MUST be stopped
    # before changing use_lvmetad to 1 and started again afterwards.
    # supported in clustered environment. If use_lvmetad=1 and locking_type=3
    use_lvmetad = 0
    #     is triggered. This requires lvmetad (global/use_lvmetad=1) and udev

This request was resolved in Red Hat Enterprise Linux 7.0.

Contact your manager or support representative in case you have further questions about the request.