Failed to install guestOS ubuntu-19.10-live-server-amd64.iso when create LVM in NVME disk

Bug #1850594 reported by vmware-gos-Yuhua on 2019-10-30
16
This bug affects 2 people
Affects Status Importance Assigned to Milestone
curtin (Ubuntu)
Undecided
Unassigned
subiquity (Ubuntu)
Undecided
Unassigned

Bug Description

Summary:
---------------------
Failed to install guestOS ubuntu-19.10-live-server-amd64.iso when choose partitioning method "Guilded - use entire disk and set up LVM" in NVME disk. Please check the attached ga_failed_partition_lvm.png

If we choose the default partitioning method "Guilded - use entire disk" in stage "Partition disks". it will succeed.

Steps to reproduce:
1. Create VM in ESXi with NVME controller, EFI and enable secure boot. the other setting is default.
2. open VMRC and mount iso ubuntu-19.10-live-server-amd64.iso
3. Power on VM, The iso is recognized and it will start to install guestOS
4. During the stage "Partition Disks", we choose "Guilded - use entire disk and set up LVM"
5. Failed to install grub during the installing process. please check attached "ga_failed_partition_lvm.png"

relative test:
Not hit the issue with same settings for beta1 image.

vmware-gos-Yuhua (yhzou) wrote :
vmware-gos-Yuhua (yhzou) wrote :

From vmware dev:
The error message (attachment ERROR_MSG.png) showed that the installer tried to label /dev/disk/by-id/wwn-nvme.xxxxxx. But the real path generated by udev is showed in (REAL_PATH.png), we can see it's /dev/disk/by-id/nvme-nvme.xxxxx. There must be something wrong with the installer or the udev rules in GOS.

vmware-gos-Yuhua (yhzou) wrote :
Launchpad Janitor (janitor) wrote :

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

Changed in subiquity (Ubuntu):
status: New → Confirmed
wwyhappy (wwthappy) wrote :

This issue should not only happen in virtualized environment but also with real bare metal with NVMe installed.

Joshua Powers (powersj) wrote :

Adding the curtin project due to the error message. There has been some clean up of other NVMe issues, so I will let someone reply if this is already fixed or is another case that needs to be fixed.

vmware-gos-Yuhua (yhzou) wrote :

this issue is fixed and verified in bug #1849322.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers