Bug 1546538
| Summary: | Provide a way to disable lvm2-lvmetad.service and lvm2-lvmetad.socket on a hypervisor | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 7 | Reporter: | Nir Soffer <nsoffer> |
| Component: | lvm2 | Assignee: | LVM and device-mapper development team <lvm-team> |
| lvm2 sub component: | Default / Unclassified | QA Contact: | cluster-qe <cluster-qe> |
| Status: | CLOSED WONTFIX | Docs Contact: | |
| Severity: | high | ||
| Priority: | unspecified | CC: | agk, heinzm, jbrassow, kailas.t.kadam, klaas, msnitzer, nkshirsa, pasik, prajnoha, teigland, zkabelac |
| Version: | 7.7 | ||
| Target Milestone: | rc | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2019-08-19 22:43:36 UTC | Type: | Bug |
| 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: | |||
| Bug Blocks: | 1462792 | ||
|
Description
Nir Soffer
2018-02-18 13:09:22 UTC
This issue pops up again when updating to rhel 7.6 beta. During update I get alarming messages like this: Updating : 7:lvm2-2.02.180-1.el7.x86_64 220/916 Failed to execute operation: Cannot send after transport endpoint shutdown Failed to start lvm2-lvmetad.socket: Unit is masked. If you won't correct this for 7.6 maybe write something into the release notes about this error being acceptable during update. (In reply to Klaas Demter from comment #2) lvmetad was removed upstream, so at least we have a long term solution: commit 117160b27e510dceb1ed6acf995115c040acd88d Author: David Teigland <teigland> Date: Tue Jul 10 13:39:29 2018 -0500 Remove lvmetad Native disk scanning is now both reduced and async/parallel, which makes it comparable in performance (and often faster) when compared to lvm using lvmetad. Autoactivation now uses local temp files to record online PVs, and no longer requires lvmetad. There should be no apparent command-level change in behavior. I hope that we can have a minimal short term change making it possible to disable lvmetad without these warnings. David, do you think this can be improved in 7.x? What does long term mean in this scenario -- is that change going to get into rhel8? If I see this correctly it's not in the latest 2.02 releases lvmetad won't be in rhel8, but it will continue to cause problems for the life of rhel7. The best solution to this whole mess would be for us to move lvmetad into a separate package that could optionally be installed/uninstalled, so if you didn't intstall the lvmetad package then you wouldn't have the lvmetad daemon or systemd files installed on the system. How does it work if you leave the unit files in place and enabled, but move the lvmetad binary somewhere else? Doing that would probably break a dozen rules, but it's basically the correct solution to the problem: we never want to allow lvmetad to run on the system. As long as the lvmetad binary exists on the system, it will be possible for an admin to start and use it, even if you completely disable all the systemd-related files. Apart from that, it sounds like it's impossible to completely disable all lvmetad-related systemd files and completely avoid all error messages. we have this issue on physical server which has 1000+ lun and we are getting this issue. we have disabled the lvmetad and trying to update the system but it is getting failed with below error. could you please help on this. Scriptlet output: 1 Failed to execute operation: Cannot send after transport endpoint shutdown 2 Failed to start lvm2-lvmetad.socket: Unit is masked. is this bug related with 3.10.0-957.21.2.el7.x86_64 kernel as we are getting issue with this kernel and server has 1000+ lun present on the server |