Please merge lvm2 from Debian unstable for lvmlockd and sanlock support

Bug #1741986 reported by Charlie Smurthwaite
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
lvm2 (Ubuntu)
Fix Released
Wishlist
Nish Aravamudan

Bug Description

I am extremely interesting in utilizing the following stack to host disks for KVM virtual machines:

* lvm2
* lvmlockd
* sanlock

I believe in order to use lvmlockd, the lvm2 sources will need to be merged from Debian and the lvm2-lockd binary package will need to be built. Please could I request that this merge happen prior to the release of Beaver.

summary: - Please merge lvmlockd with sanlock support
+ Please merge lvmlockd and sanlock support
Nish Aravamudan (nacc)
summary: - Please merge lvmlockd and sanlock support
+ Please merge lvm2 from Debian unstable for lvmlockd and sanlock support
Changed in lvm2 (Ubuntu):
status: New → Confirmed
importance: Undecided → Wishlist
assignee: nobody → Nish Aravamudan (nacc)
milestone: none → ubuntu-18.02
Revision history for this message
TJ (tj) wrote :

Having this in 18.04 LTS would be extremely useful for use by hosting operations to streamline required packages (avoiding the need for clvmd + dlm, and in some scenarios corosync).

Revision history for this message
Charlie Smurthwaite (charlie-d) wrote :

I have raised another bug with Debian regarding user permissions in sanlock that relates to this. This is not critical (or necessarily even relevant) to this merge, but I thought I'd mention it in case the fix can be pulled in at the same time: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=888102

Changed in lvm2 (Ubuntu):
status: Confirmed → Fix Committed
Revision history for this message
Julian Andres Klode (juliank) wrote :

This is stuck in proposed because we need to either MIR sanlock or demote lvm2-lockd to universe.

Revision history for this message
Julian Andres Klode (juliank) wrote :
Download full text (3.8 KiB)

Fixed in 2.02.176-4.1ubuntu2

lvm2 (2.02.176-4.1ubuntu2) bionic; urgency=medium

  * Demote Recommends: thin-provisioning-tools to Suggests, as it's not
    in main.

lvm2 (2.02.176-4.1ubuntu1) bionic; urgency=low

  * Merge with Debian unstable. Remaining changes:
    - Add and install clvmd resource agent
    - Lower libdevmapper1.02.1's Depends: dmsetup to a Recommends:. This
      breaks the circular dependency that causes upgrade failures. As dmsetup
      is "Priority: required", this has no other practical consequences.
    - debian/control: add dmsetup-udeb to libdevmapper1.02.1-udeb recommends.
    - debian/dmsetup-udeb.install: install udev rules in udebs
      (Debian #504341).
    - Add debian/initramfs-tools/lvm2/scripts/init-bottom/lvm2: We cannot
      properly synthesize LVM LV change events with udevadm trigger, so
      if we use LVM, we need to let it finish; otherwise we get missing LV
      symlinks.
    - Add debian/initramfs-tools/lvm2/scripts/init-premount/lvm2: failure
      hooks to help fix bad boots (Debian #468115)
    - Do not start lvmetad when inside a container.
    - Add enable-issue-discards.patch: Enable "issue_discards" option by
      default to trim SSDs when changing PVs. This option has no effect if the
      kernel or the drive does not support trimming, so it's safe to enable by
      default. (Debian #717313)
    - debian/rules:
      + Copy .po file to .pot file for Rosetta (Ubuntu specific).
    - debian/initramfs-tools/lvm2/hooks/lvm2: depend on udev since
      we ship udev rules.
    - debian/clvm.maintscripts: Drop the /etc/default/clvm conffile on
      upgrade. This delta can be dropped after 18.04 release.
    - Do not start lvm2-monitor in containers (LP #1576341)
  * Dropped, merged upstream:
    - Add a patch to fix crashes on 32bit platforms:
      + 0013-fix-lvmetad-32bit.patch
    - d/p/fix-strips-limit.patch: Fix regression limiting number of
      stripes to 8 (LP #1675770)

lvm2 (2.02.176-4.1) unstable; urgency=high

  * Non-maintainer upload.
  * Revert uncoordinated addition of udev rules/sync support in udebs
    which breaks LVM support in debian-installer instead of getting
    debian-installer and installed systems to agree on device names.
    (closes: #883361, reopens: #504341)

lvm2 (2.02.176-4) unstable; urgency=medium

  * Don't try to add dropped udev rules to initramfs.

lvm2 (2.02.176-3) unstable; urgency=medium

  * Actually add newly installed udev rules to initramfs.
    (closes: #881314)
  * Make initramfs hooks bail out if udev rules can't be found.
  * Copy complete lvm config into initramfs.

lvm2 (2.02.176-2) unstable; urgency=medium

  * Drop changes for upgrades from before Wheezy.
  * Drop deprecated python bindings.
  * Enable udev rules in udeb. (closes: #504341)
  * Drop some udev rules modifications.
    - Pull in newer dmsetup for udev rules changes.

lvm2 (2.02.176-1) unstable; urgency=medium

  * New upstream release.
  * Drop obsolte build-depends on dh-systemd.
  * Drop extra priorities from packages.
  * Update Standards-Version to 4.1.1, no changes.
  * Make lvm2-dbusd depend manually on required modules. (closes: #880543)
  * Make lvm2 recomme...

Read more...

Changed in lvm2 (Ubuntu):
status: Fix Committed → Fix Released
tags: added: id-5a6b600931df673b25128006
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.