Bug 1166174
| Summary: | 69-dm-lvm-metad.rules calls systemd-run | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 6 | Reporter: | Jan Kurik <jkurik> |
| Component: | lvm2 | Assignee: | LVM and device-mapper development team <lvm-team> |
| Status: | CLOSED ERRATA | QA Contact: | cluster-qe <cluster-qe> |
| Severity: | urgent | Docs Contact: | |
| Priority: | urgent | ||
| Version: | 6.6 | CC: | agk, amureini, bmr, cmarthal, dwysocha, fdeutsch, fsimonce, heinzm, jbrassow, jkurik, mjuricek, mkarg, msnitzer, nsoffer, pablo.iranzo, pm-eus, prajnoha, prockai, rjones, tdosek, thornber, zkabelac |
| Target Milestone: | rc | Keywords: | Regression, ZStream |
| Target Release: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | lvm2-2.02.111-2.el6_6.1 | Doc Type: | Bug Fix |
| Doc Text: |
A bug in lvm2 configuration script caused improper detection of environment used which ended up with incorrect udev rules for lvmetad notification to be generated (/lib/udev/rules.d/69-dm-lvm-metad.rules). These rules contained incorrect calls specific for systemd environment only which is not present in RHEL6. As a consequence, if lvmetad was used (global/use_lvmetad=1 lvm.conf option), then lvmetad daemon missed notifications about PVs present in the system and lvmetad could not provide proper cached information to LVM tools. This also caused any LVs to not autoactivate when all the PVs making up the VG were present in the system.
|
Story Points: | --- |
| Clone Of: | 1165596 | Environment: | |
| Last Closed: | 2014-11-26 09:36:34 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | 1165596 | ||
| Bug Blocks: | 1153323 | ||
|
Description
Jan Kurik
2014-11-20 13:58:58 UTC
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-2014-1909.html |