[Bug 332950] Re: Misleading "cryptsetup: WARNING: invalid line in /etc/crypttab - "

[Roel Van de Paar]

This seems still flaky even in 17.04.

# cat /etc/crypttab
nvme0n1p3_crypt	UUID="20eada6e-6b8c-4e19-b612-524ea2a131ff"   none luks,discard
# update-initramfs -k 4.10.0-24-generic -c -b /boot
update-initramfs: Generating /boot/initrd.img-4.10.0-24-generic
cryptsetup: WARNING: Invalid source device UUID="20eada6e-6b8c-4e19-b612-524ea2a131ff"
cryptsetup: WARNING: Invalid source device UUID="20eada6e-6b8c-4e19-b612-524ea2a131ff"
W: mdadm: /etc/mdadm/mdadm.conf defines no arrays.

# vi /etc/crypttab
# cat /etc/crypttab
nvme0n1p3_crypt	UUID=20eada6e-6b8c-4e19-b612-524ea2a131ff   none luks,discard
# update-initramfs -k 4.10.0-24-generic -c -b /boot
update-initramfs: Generating /boot/initrd.img-4.10.0-24-generic
W: mdadm: /etc/mdadm/mdadm.conf defines no arrays.

In other words, when the UUID is quoted (") it fails. However, the
quoted UUID is exactly what at least one of the other tools in Ubuntu
must use because there was a second line in that file originally (I
removed it to make the example/testcase above clearer) for another drive
and that one uses quotes.

Please review and QA this area properly. Thank you.

** Also affects: cryptsetup
   Importance: Undecided
       Status: New

** No longer affects: cryptsetup

-- 
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/332950

Title:
  Misleading "cryptsetup: WARNING: invalid line in /etc/crypttab - "

Status in cryptsetup package in Ubuntu:
  Fix Released
Status in cryptsetup source package in Lucid:
  Won't Fix
Status in cryptsetup source package in Maverick:
  Won't Fix
Status in cryptsetup package in Debian:
  Fix Released

Bug description:
  Binary package hint: cryptsetup

  When there's no line for the cryptsetup root device, a misleading warning is issued during update-initramfs:
    cryptsetup: WARNING: invalid line in /etc/crypttab -

  I'm attaching a patch that handles this better, by outputting
    cryptsetup: WARNING: Missing line in /etc/crypttab for $target
  in this case.

  I've ran into this when manually doing the "mdadm-cryptsetup-
  lvm2-initramfs" dance, and used another name during "cryptsetup
  luksOpen".

  ProblemType: Bug
  Architecture: i386
  DistroRelease: Ubuntu 9.04
  NonfreeKernelModules: nvidia
  Package: cryptsetup 2:1.0.6-7ubuntu5 [modified: usr/share/initramfs-tools/hooks/cryptroot]
  ProcEnviron:
   LANGUAGE=
   PATH=(custom, user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: cryptsetup
  Uname: Linux 2.6.28-8-generic i686

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