Bug ID 1017574
Summary Dependency loop with cryptsetup key file on filesystem due to lvm2-activation.service
Classification openSUSE
Product openSUSE Tumbleweed
Version Current
Hardware Other
OS Other
Status NEW
Severity Normal
Priority P5 - None
Component Basesystem
Assignee bnc-team-screening@forge.provo.novell.com
Reporter arvidjaar@gmail.com
QA Contact qa-bugs@suse.de
Found By ---
Blocker ---

Dec 30 04:17:47 localhost kernel: Command line:
BOOT_IMAGE=/boot/vmlinuz-4.9.0-2-default
root=UUID=3391002a-3ede-4037-8fd5-6c70b8b9465c resume=/dev/sda1 splash=silent
quiet showopts luks.key=/key/sdb2.key
luks.uuid=502cca08-a4ff-4592-a5cc-ec4ef6650200
...
Dec 30 04:17:52 localhost systemd[1]:
systemd-cryptsetup@luks\x2d502cca08\x2da4ff\x2d4592\x2da5cc\x2dec4ef6650200.service:
Found ordering cycle on
systemd-cryptsetup@luks\x2d502cca08\x2da4ff\x2d4592\x2da5cc\x2dec4ef6650200.service/start
Dec 30 04:17:52 localhost systemd[1]:
systemd-cryptsetup@luks\x2d502cca08\x2da4ff\x2d4592\x2da5cc\x2dec4ef6650200.service:
Found dependency on key.mount/start
Dec 30 04:17:52 localhost systemd[1]:
systemd-cryptsetup@luks\x2d502cca08\x2da4ff\x2d4592\x2da5cc\x2dec4ef6650200.service:
Found dependency on local-fs-pre.target/start
Dec 30 04:17:52 localhost systemd[1]:
systemd-cryptsetup@luks\x2d502cca08\x2da4ff\x2d4592\x2da5cc\x2dec4ef6650200.service:
Found dependency on lvm2-activation.service/start
Dec 30 04:17:52 localhost systemd[1]:
systemd-cryptsetup@luks\x2d502cca08\x2da4ff\x2d4592\x2da5cc\x2dec4ef6650200.service:
Found dependency on cryptsetup.target/start
Dec 30 04:17:52 localhost systemd[1]:
systemd-cryptsetup@luks\x2d502cca08\x2da4ff\x2d4592\x2da5cc\x2dec4ef6650200.service:
Found dependency on
systemd-cryptsetup@luks\x2d502cca08\x2da4ff\x2d4592\x2da5cc\x2dec4ef6650200.service/start
Dec 30 04:17:52 localhost systemd[1]:
systemd-cryptsetup@luks\x2d502cca08\x2da4ff\x2d4592\x2da5cc\x2dec4ef6650200.service:
Breaking ordering cycle by deleting job key.mount/start
Dec 30 04:17:52 localhost systemd[1]: key.mount: Job key.mount/start deleted to
break ordering cycle starting with
systemd-cryptsetup@luks\x2d502cca08\x2da4ff\x2d4592\x2da5cc\x2dec4ef6650200.service/start


So /key is not mounted (or at least it is not guaranteed to be mounted *before*
cryptsetup service) and encrypted container not activated.


You are receiving this mail because: