Bug 1462792 - RHV-H - systemd: Cannot add dependency job for unit lvm2-lvmetad.socket, ignoring: Unit is masked.
RHV-H - systemd: Cannot add dependency job for unit lvm2-lvmetad.socket, igno...
Status: NEW
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: vdsm (Show other bugs)
4.1.2
Unspecified Unspecified
medium Severity medium
: ovirt-4.1.7
: ---
Assigned To: Nir Soffer
Raz Tamir
: Reopened
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2017-06-19 10:33 EDT by Marian Jankular
Modified: 2017-08-31 05:53 EDT (History)
19 users (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2017-06-27 07:45:26 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: Storage
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Marian Jankular 2017-06-19 10:33:37 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):
redhat-release-virtualization-host-4.1-2.1.el7.x86_64
version below 4.1-2 as well

How reproducible:
everytime

Steps to Reproduce:
1. install rhvh
2. boot it
3. check /var/log/messages

Actual results:
systemd: Cannot add dependency job for unit lvm2-lvmetad.socket, ignoring: Unit is masked.

Expected results:
as lvm2-lvmetad is disabled i would expect that is would not be as any dependency for service

Additional info:
Comment 1 Sandro Bonazzola 2017-06-20 05:39:14 EDT
Nir, is there any functional implication here other than the warning?
Comment 2 Nir Soffer 2017-06-20 05:46:54 EDT
This bug should move to lvm. I don't
know why lvm is logging warnings about
disabled and msaked service.
Comment 3 Sandro Bonazzola 2017-06-27 05:41:35 EDT
Nir, moving to you,, can you please handle the move to lvm?
Comment 5 Peter Rajnoha 2017-06-27 07:45:26 EDT
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.
Comment 6 Nir Soffer 2017-06-27 07:59:34 EDT
Thanks Peter, moving the bug to vdsm, we will change the configuration.
Comment 9 Nir Soffer 2017-06-27 08:01:51 EDT
Tal, this should be a trivial change, do you want to schedule it to 4.1.4?
Comment 10 Allon Mureinik 2017-06-27 09:01:22 EDT
(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.
Comment 12 Allon Mureinik 2017-07-02 16:38:09 EDT
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.

Note You need to log in before you can comment on or make changes to this bug.