[Bug 1776626] Autopkgtest regression report (systemd/237-3ubuntu10.31)

[Ubuntu SRU Bot]

All autopkgtests for the newly accepted systemd (237-3ubuntu10.31) for bionic have finished running.
The following regressions have been reported in tests triggered by the package:

gvfs/1.36.1-0ubuntu1.3.3 (ppc64el, amd64)
netplan.io/0.97-0ubuntu1~18.04.1 (amd64)
apt/1.6.12 (arm64, ppc64el)
pulseaudio/unknown (armhf)


Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/bionic/update_excuses.html#systemd

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  [18.10 FEAT] Support 4k sectors for fast clear key dm-crypt - crypttab
  part

Status in Ubuntu on IBM z Systems:
  Fix Released
Status in cryptsetup package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in cryptsetup source package in Bionic:
  Won't Fix
Status in systemd source package in Bionic:
  Fix Committed

Bug description:
  [Impact]

   * cryptsetup in bionic supports creating luks volumes with a non-
  standard sector-size option, and thus this option also needs to be
  used when activating the LUKS volumes. Add sector-size= option support
  to /etc/crypttab.

  [Test Case]

   * Create a plain LUKS volume with sector-size 4096
   * Specify sector-size=4096 option in /etc/crypttab
   * reload systemd, start systemd-cryptsetup at .service for that volume
   * check the journal, to ensure that `sector-size` option was recognized and is active. (i.e. there is not error messages about unrecognized option `sector-size` from systemd-cryptsetup)

  [Regression Potential]

   * This is an optional argument, not used by default. Currently custom
  sector-size crypttab does not work correctly, and thus cannot regress.

  [Other Info]
   
   * Original bug report

  Support fast clear key dm-crypt with 4k support

  Extend /etc/crypttab  to enable 4k sector support in plain mode

  The proposed enhancements are posted on github, see
       https://github.com/systemd/systemd/issues/8881

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1776626/+subscriptions