Red Hat Bugzilla – Bug 1462792
RHV-H - systemd: Cannot add dependency job for unit lvm2-lvmetad.socket, ignoring: Unit is masked.
Last modified: 2017-08-31 05:53:15 EDT
Description of problem:
during rhvh boot following message appears
"systemd: Cannot add dependency job for unit lvm2-lvmetad.socket, ignoring: Unit is masked."
Version-Release number of selected component (if applicable):
version below 4.1-2 as well
Steps to Reproduce:
1. install rhvh
2. boot it
3. check /var/log/messages
systemd: Cannot add dependency job for unit lvm2-lvmetad.socket, ignoring: Unit is masked.
as lvm2-lvmetad is disabled i would expect that is would not be as any dependency for service
Nir, is there any functional implication here other than the warning?
This bug should move to lvm. I don't
know why lvm is logging warnings about
disabled and msaked service.
Nir, moving to you,, can you please handle the move to lvm?
Please, do not mask lvm2-lvmetad.socket - it's used by lvm2-lvmetad.service and also referenced in various other systemd units and you would need to mask them too for this to be complete (but you don't need to this at all).
If you disable lvmetad in lvm.conf (use_lvmetad=0), then lvm tools will not use lvmetad and hence they won't initiate a connection through lvmetad socket. So there's no gain in masking the lvm2-lvmetad.socket - it's simply not used. Just keep the lvm2-lvmetad.socket as it is, do not mask it please.
Thanks Peter, moving the bug to vdsm, we will change the configuration.
Tal, this should be a trivial change, do you want to schedule it to 4.1.4?
(In reply to Nir Soffer from comment #9)
> Tal, this should be a trivial change, do you want to schedule it to 4.1.4?
If it's really that trivial, yes please.
We should strive to fix bugs with customer tickets as early as possible.
4.1.4 is planned as a minimal, fast, z-stream version to fix any open issues we may have in supporting the upcoming EL 7.4.
Pushing out anything unrelated, although if there's a minimal/trival, SAFE fix that's ready on time, we can consider introducing it in 4.1.4.