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:

69-dm-lvm-metad.rules has a line (92) that reads

ACTION!="remove", ENV{LVM_PV_GONE}=="1", RUN+="/bin/systemd-run $env{LVM_SBIN_PATH}/lvm pvscan --cache $major:$minor", GOTO="lvm_end"

Since RHEL 6.6 does not have systemd this will never work.

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

lvm2-2.02.111-2.el6.x86_64

How reproducible:

always

Steps to Reproduce:

1. add fcoe block devices that contain PV, VG, LV

Actual results:

No automatical activation of LVM on those block devices.

Expected results:

Automatical activation of all available PV, VGs and LVs

Additional info:

(In reply to Marko Karg from comment #0)
> Description of problem:
> 
> 69-dm-lvm-metad.rules has a line (92) that reads
> 
> ACTION!="remove", ENV{LVM_PV_GONE}=="1", RUN+="/bin/systemd-run
> $env{LVM_SBIN_PATH}/lvm pvscan --cache $major:$minor", GOTO="lvm_end"
> 

That should have been "pvscan --background ..." for RHEL6! It's configuration error - we made the "--enable-udev-systemd-background-jobs" default, however, we don't have master switch to disable systemd - we need one - either automatic or a new configure option.

Configure now checks for proper systemd environment and disables these specific code/rules if systemd is not available:

https://git.fedorahosted.org/cgit/lvm2.git/commit/?id=74ed1ba9f99aaf16906d53c28ad604eaa7a21419

The fix will be delivered to 6.7 as part of the lvm2 rebase. The 6.6 is fixed via z-stream (2.02.111-2.el6_6.1).

Line 92 now reads a proper:

pvscan --background --cache ...etc.

systemd is not mentioned anywhere. 

Marking this as verified with:

lvm2-2.02.118-1.el6.x86_64

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://rhn.redhat.com/errata/RHBA-2015-1411.html