lvm2-lvmlocking.service incorrectly uses nonexistent option --lock-opt autowait

Bug #1874142 reported by WGH
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
lvm2 (Ubuntu)
New
Undecided
Unassigned

Bug Description

The lvm2-lvmlocking.service systemd unit installed by lvm2-lockd package has the following line:

# start lockspaces and wait for them to finish starting
ExecStart=@SBINDIR@/lvm vgchange --lock-start --lock-opt autowait

This is unfortunately wrong: the autowait option was dropped in this commit: https://www.redhat.com/archives/lvm-devel/2015-July/msg00091.html, and attempting to specify it causes the opposite effect: no waiting is done at all.

It should've said --lock-opt auto.

Revision history for this message
WGH (wgh) wrote :

https://www.redhat.com/archives/lvm-devel/2020-April/msg00017.html fixed upstream, but still affects both Ubuntu 18.04 and 20.04 (/lib/systemd/system/lvm2-lvmlocking.service and /lib/systemd/system/lvmlocks.service correspondingly)

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.