System fails to start encrypted swap on boot on an encrypted home installation

Bug #1713722 reported by Jean-Baptiste Lallement on 2017-08-29
20
This bug affects 4 people
Affects Status Importance Assigned to Milestone
cryptsetup (Ubuntu)
High
Mathieu Trudel-Lapierre

Bug Description

artful desktop 20170829

Test Case
1. Install Ubuntu with the default settings (in particular use guided partitioning "Erase everything") and in the user setup select "Encrypt my home directory"
2. Proceed with the installation and reboot at the end of the instation

Expected result
The system boots successfully

Actual result
It takes a very long time to boot
The following entries are recorded in the journal

août 29 14:41:14 ubuntu systemd[1]: Dependency failed for /dev/mapper/cryptswap1.
-- Subject: Unit dev-mapper-cryptswap1.swap has failed
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
--
-- Unit dev-mapper-cryptswap1.swap has failed.
--
-- The result is dependency.
août 29 14:41:14 ubuntu systemd[1]: dev-mapper-cryptswap1.swap: Job dev-mapper-cryptswap1.swap/start failed with result 'dependency'.
août 29 14:41:14 ubuntu systemd[1]: dev-mapper-cryptswap1.device: Job dev-mapper-cryptswap1.device/start failed with result 'timeout'.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: cryptsetup 2:1.7.2-0ubuntu4
ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
Uname: Linux 4.12.0-11-generic x86_64
ApportVersion: 2.20.6-0ubuntu7
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Tue Aug 29 14:45:22 2017
EcryptfsInUse: Yes
InstallationDate: Installed on 2017-08-29 (0 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170829)
SourcePackage: cryptsetup
UpgradeStatus: No upgrade log present (probably fresh install)
cmdline: BOOT_IMAGE=/boot/vmlinuz-4.12.0-11-generic root=UUID=4d39aadd-ed92-4d46-869f-4ae2e0708212 ro
crypttab: cryptswap1 UUID=bc44a25c-99bd-4c30-8db8-6b642d17e199 /dev/urandom swap,offset=1024,cipher=aes-xts-plain64

Jean-Baptiste Lallement (jibel) wrote :
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in cryptsetup (Ubuntu):
status: New → Confirmed
Changed in cryptsetup (Ubuntu):
importance: Undecided → High
Ubuntu QA Website (ubuntuqa) wrote :

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1713722

tags: added: iso-testing
description: updated
Changed in cryptsetup (Ubuntu):
status: Confirmed → In Progress
assignee: nobody → Mathieu Trudel-Lapierre (cyphermox)
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers