[Bug 1874142] [NEW] lvm2-lvmlocking.service incorrectly uses nonexistent option --lock-opt autowait

[WGH]

Public bug reported:

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.

** Affects: lvm2 (Ubuntu)
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to lvm2 in Ubuntu.
https://bugs.launchpad.net/bugs/1874142

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

Status in lvm2 package in Ubuntu:
  New

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.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1874142/+subscriptions