I wasn't able to re-create this on my LPAR (also using zFCP storage,
installed with subiquity):

$ apt-cache policy s390-tools-zkey
s390-tools-zkey:
  Installed: (none)
  Candidate: 2.12.0-0ubuntu3
  Version table:
     2.12.0-0ubuntu3 500
        500 http://ports.ubuntu.com/ubuntu-ports focal/main s390x Packages
        500 http://us.ports.ubuntu.com/ubuntu-ports focal/main s390x Packages
$ sudo apt install s390-tools-zkey
Reading package lists... Done
Building dependency tree       
Reading state information... Done
The following NEW packages will be installed:
  s390-tools-zkey
0 upgraded, 1 newly installed, 0 to remove and 1 not upgraded.
Need to get 98.6 kB of archives.
After this operation, 393 kB of additional disk space will be used.
Get:1 http://ports.ubuntu.com/ubuntu-ports focal/main s390x s390-tools-zkey 
s390x 2.12.0-0ubuntu3 [98.6 kB]
Fetched 98.6 kB in 0s (372 kB/s)           
Selecting previously unselected package s390-tools-zkey.
(Reading database ... 144203 files and directories currently installed.)
Preparing to unpack .../s390-tools-zkey_2.12.0-0ubuntu3_s390x.deb ...
Unpacking s390-tools-zkey (2.12.0-0ubuntu3) ...
Setting up s390-tools-zkey (2.12.0-0ubuntu3) ...
Adding group `zkeyadm' (GID 119) ...
Done.
Processing triggers for man-db (2.9.1-1) ...
Processing triggers for initramfs-tools (0.136ubuntu6) ...
update-initramfs: Generating /boot/initrd.img-5.4.0-29-generic
Using config file '/etc/zipl.conf'
Run /lib/s390-tools/zipl_helper.device-mapper /boot
Building bootmap in '/boot'
Adding IPL section 'ubuntu' (default)
Preparing boot device: dm-0.
Done.
$ sudo apt install s390-tools-zkey
Reading package lists... Done
Building dependency tree       
Reading state information... Done
s390-tools-zkey is already the newest version (2.12.0-0ubuntu3).
0 upgraded, 0 newly installed, 0 to remove and 1 not upgraded.
$ sudo apt install --reinstall s390-tools-zkey
Reading package lists... Done
Building dependency tree       
Reading state information... Done
0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 1 not upgraded.
Need to get 98.6 kB of archives.
After this operation, 0 B of additional disk space will be used.
Get:1 http://ports.ubuntu.com/ubuntu-ports focal/main s390x s390-tools-zkey 
s390x 2.12.0-0ubuntu3 [98.6 kB]
Fetched 98.6 kB in 0s (376 kB/s)           
(Reading database ... 144213 files and directories currently installed.)
Preparing to unpack .../s390-tools-zkey_2.12.0-0ubuntu3_s390x.deb ...
Unpacking s390-tools-zkey (2.12.0-0ubuntu3) over (2.12.0-0ubuntu3) ...
Setting up s390-tools-zkey (2.12.0-0ubuntu3) ...
Processing triggers for man-db (2.9.1-1) ...
Processing triggers for initramfs-tools (0.136ubuntu6) ...
update-initramfs: Generating /boot/initrd.img-5.4.0-29-generic
Using config file '/etc/zipl.conf'
Run /lib/s390-tools/zipl_helper.device-mapper /boot
Building bootmap in '/boot'
Adding IPL section 'ubuntu' (default)
Preparing boot device: dm-0.
Done.
$

$ apt-cache policy cryptsetup
cryptsetup:
  Installed: 2:2.2.2-3ubuntu2
  Candidate: 2:2.2.2-3ubuntu2
  Version table:
 *** 2:2.2.2-3ubuntu2 500
        500 http://ports.ubuntu.com/ubuntu-ports focal/main s390x Packages
        500 http://us.ports.ubuntu.com/ubuntu-ports focal/main s390x Packages
        100 /var/lib/dpkg/status

Did that happen on a system that was installed with d-i legacy or with
subiquity?

And I cannot find any indication that a package related to this (like
initramfs-tools or cryptsetup) was updated after 20.04 release. There
was a cryptsetup ticket short before 20.04 GA (LP 1864360), but it looks
unrelated to this...

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

Title:
  Installing package s390-tools-zkey reports cryptsetup: ERROR: Couldn't
  resolve device

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/s390-tools/+bug/1874138/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to