https://bugzilla.suse.com/show_bug.cgi?id=1222087 https://bugzilla.suse.com/show_bug.cgi?id=1222087#c2 Antonio Feijoo <antonio.feijoo@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |antonio.feijoo@suse.com --- Comment #2 from Antonio Feijoo <antonio.feijoo@suse.com> --- (In reply to Nicolas FORMICHELLA from comment #0)

Steps to Reproduce: 1. Install Tumbleweed with /home (or other) partition encrypted

I think that in order to reproduce your issue, you also have to manually set the DPS Partition ID using YaST or gdisk, because the default just sets the "Linux" type, and the systemd-gpt-auto-generator does not recognize any partitions and does not do create any device unit at boot in this case.

After investigation I found that both `systemd-gpt-auto-generator` and `systemd-cryptsetup-generator` create a service for the same partition.

What is happening is documented in the systemd-gpt-auto-generator(8) man page: "The /home/, /srv/, /var/, /var/tmp/ and swap partitions may be encrypted in LUKS format. In this case, a device mapper device is set up under the names /dev/mapper/home, /dev/mapper/srv, /dev/mapper/var, /dev/mapper/tmp or /dev/mapper/swap. Note that this might create conflicts if the same partition is listed in /etc/crypttab with a different device mapper device name." If you have an encrypted partition with the DPS UUID, you need to disable the systemd-gpt-auto-generator by adding `systemd.gpt_auto=0` to the kernel command line, or remove its entry from /etc/crypttab. -- You are receiving this mail because: You are on the CC list for the bug.