Crash and failure installing focal
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
subiquity |
Fix Released
|
Undecided
|
Unassigned | ||
curtin (Ubuntu) |
Fix Released
|
High
|
Ryan Harper | ||
Eoan |
Invalid
|
Undecided
|
Unassigned | ||
Focal |
Fix Released
|
High
|
Ryan Harper | ||
util-linux (Debian) |
Fix Released
|
Unknown
|
|||
util-linux (Ubuntu) |
Fix Released
|
Medium
|
Mauricio Faria de Oliveira | ||
Eoan |
Fix Released
|
Medium
|
Mauricio Faria de Oliveira | ||
Focal |
Fix Released
|
Medium
|
Mauricio Faria de Oliveira |
Bug Description
[Impact]
* lsblk no longer prints a partition's parent
kernel device name (the wholedisk).
(i.e., 'lsblk -no PKNAME /dev/partition')
* Another impact is the 'removable media' check
always return zero for partitions.
(i.e., 'lsblk -no RM /dev/partition')
* The regression was introduced on v2.34, only
Eoan (v2.34) and later are affected.
Disco (v2.33) and earlier are not affected.
* The regression is fixed in v2.35, in commit
e3bb9bfb76c1 ("lsblk: force to print PKNAME
for partition"); fixes RM for partition too.
[Test Case]
* $ lsblk -no PKNAME /dev/vda1 # partition
* Expected output: vda # wholedisk
* Current output: (nothing)
* $ lsblk -no RM /dev/sdb1 # partition in removable disk
* Expected output: 1 # removable media
* Current output: 0 # not removable media
[Regression Potential]
* Columns that depend on a partition device's
parent device (i.e., seen as 'wholedisk')
could in theory show incorrect values if
another bug is present in v2.34 for that.
* Other usages of 'parent' pointer in the
function have been examined and reported
(e.g. issue w/ removable media column),
and others found to not have issues
(e.g. --merge option, to group multiple
parents of a device, as in RAID.)
[Other Info]
* The impacts to the curtin source package
have been addressed in other way, it no
longer requires util-linux, comment #14.
* util-linux github issue:
https:/
[Original Bug Description]
During an install of the daily live image for 20.04 Ubuntu Server, the installer first crashed and restarted itself, then failed to install the system.
Attached are the logs left on the install USB key.
Related branches
- Ryan Harper (community): Approve
- Server Team CI bot: Approve (continuous-integration)
- Lee Trager (community): Approve
- Dan Watkins (community): Approve
-
Diff: 369 lines (+234/-8)5 files modifiedcurtin/commands/curthooks.py (+1/-0)
examples/tests/uefi_reuse_esp.yaml (+105/-0)
helpers/common (+60/-2)
tests/vmtests/__init__.py (+16/-6)
tests/vmtests/test_reuse_uefi_esp.py (+52/-0)
Changed in curtin (Ubuntu): | |
importance: | Undecided → High |
status: | New → Triaged |
tags: | added: rls-ff-incoming |
Changed in curtin (Ubuntu Eoan): | |
status: | New → Invalid |
Changed in util-linux (Debian): | |
status: | Unknown → New |
Changed in curtin (Ubuntu Focal): | |
assignee: | nobody → Ryan Harper (raharper) |
status: | Triaged → In Progress |
tags: | removed: rls-ff-incoming |
tags: | added: sts-sponsor-mfo |
tags: | added: patch |
tags: | removed: champagne |
Changed in util-linux (Debian): | |
status: | New → Confirmed |
Changed in util-linux (Debian): | |
status: | Confirmed → Fix Released |
Changed in subiquity: | |
status: | New → Fix Released |
tags: | removed: sts-sponsor-mfo |
Hrm, this is a strange install.
The storage config has some strange settings..., first nothing is modified at all, all disks and partitions are marked preserve = true, as well as all filesystems. There is this strange mount:
{
"device": "format-0",
"id": "mount-0",
"path": "",
"type": "mount"
},
Heres the rootfs
{ partition- sda3",
"device": "format-
"id": "mount-2",
"path": "/",
"type": "mount"
},
And EFI
{ partition- sda1",
"device": "format-
"id": "mount-1",
"path": "/boot/efi",
"type": "mount"
}
The failure appears here:
+ [ -f /boot/efi/ EFI/ubuntu/ grubx64. efi ] EFI/ubuntu/ shimx64. efi ] shimx64. efi \EFI\ubuntu\ shimx64. efi shimx64. efi
+ [ -z ]
+ [ -f /boot/efi/
+ break
+ echo /EFI/ubuntu/
+ sed s|/|\\|g
+ loader=
+ efibootmgr --create --write-signature --label ubuntu --disk /dev/ --part 1 --loader \EFI\ubuntu\
efibootmgr: ** Warning ** : Boot0000 has same label ubuntu
Could not prepare Boot variable: Success
failed to install grub!
There's a but in the install-grub helper in how it determines the disk device;