[Bug 1861655] Comment bridged from LTC Bugzilla
Dimitri John Ledkov
launchpad at surgut.co.uk
Tue Apr 7 21:52:18 UTC 2020
Yes, I have managed to reproduce this recent regression in KVM. And fixes
are currently awaiting review. Unfortunately it means, we need to pause
testing for this issue until probert & apport updates land on the daily iso
in the coming days. Hopefully before we the long 4 day weekend due to
public holidays.
On Tue, 7 Apr 2020, 18:16 bugproxy, <bugproxy at us.ibm.com> wrote:
> ------- Comment From mranweil at us.ibm.com 2020-04-07 13:06 EDT-------
> We did this from petitboot (the boot loader), the current daily-pending
> iso was loop mounted and available:
>
> # wget http://ltc-wspoon3.aus.stglabs.ibm.com/mnt/casper/vmlinux
> Connecting to ltc-wspoon3.aus.stglabs.ibm.com (9.40.193.87:80)
> vmlinux 100% |********************************| 26.8M
> 0:00:00 ETA
> # wget http://ltc-wspoon3.aus.stglabs.ibm.com/mnt/casper/initrd.gz
> Connecting to ltc-wspoon3.aus.stglabs.ibm.com (9.40.193.87:80)
> initrd.gz 100% |********************************| 82.3M
> 0:00:00 ETA
> # md5sum vmlinux initrd.gz
> c3dcf1cff9d0f6cc649e8ce6cb9066eb vmlinux
> 185ba7de2818fc6ee47931342cd89f4d initrd.gz
> # kexec -l ./vmlinux --initrd=./initrd.gz --append="ip=9.3.90.144::
> 9.3.90.1:255.
> 255.255.0:ltc-wcwsp3:enP5p1s0f0:none:9.3.1.200 url=
> http://cdimage.ubuntu.com/ubu
> ntu-server/daily-live/pending/focal-live-server-ppc64el.iso
> <http://cdimage.ubuntu.com/ubuntu-server/daily-live/pending/focal-live-server-ppc64el.iso>
> --quiet"
> #
>
> With this we aren't getting as far, when the iso comes up to the
> language selection screen I get:
>
> [ ERROR: hook /usr/share/apport/general-hooks/powerpc.py crashed:
> [ Asturianu ? ] Traceback
> (most recent call last):
> [ Catal? ? ]
> File
> "/snap/subiquity/1625/usr/lib/python3/dist-packages/apport/report.py", line
> 218, in _run_hook
> [ Nederlands ? ]
> symb['add_info'](report, ui) [ Suomi
> ? ]
> File "/usr/share/apport/general-hooks/powerpc.py", line 42, in add_info
> [ Deutsch ? ]
> is_kernel = report['ProblemType'].startswith('Kernel') or 'linux' in
> report.get('Package')]
> [ Magyar ? TypeError: argument of type
> 'NoneType' is not iterable
> [ Latvie?u ? ]
> ERROR: hook
> /usr/share/apport/general-hooks/powerpc.py crashed: ]
> [ Polski ?Traceback (most recent call
> last):
> [ ??????? ? ]
> File
> "/snap/subiquity/1625/usr/lib/python3/dist-packages/apport/report.py", line
> 218, in _run_hook
> [ ?????????? ? ]
> symb['add_info'](report, ui)
> File "/usr/share/apport/general-hooks/powerpc.py", line 42, in add_info
> is_kernel = report['ProblemType'].startswith('Kernel') or 'linux' in
> report.get('Package')e
> TypeError: argument of type 'NoneType' is not iterablee
>
> Ubuntu Focal Fossa (development branch) ubuntu-server hvc0
>
> If I go and view error reports:
> ? Select an error report to view: ?
> ? ?
> ? DATE KIND STATUS ?
> ? [ Tue Apr 7 16:59:08 2020 Disk probe failure UNVIEWED ] ?
> ? [ Tue Apr 7 16:59:08 2020 Block device probe failure UNVIEWED ] ?
> ? [ ??? Disk probe failure UNVIEWED ] ?
> ? [ ??? Block device probe failure UNVIEWED ] ?
> ? [ ??? Disk probe failure UNVIEWED ] ?
> ? [ ??? Block device probe failure UNVIEWED ] ?
> ? ?
> ? [ Close ] ?
> ?
>
> ? Sorry, there was a problem examining the storage devices on this ?
> ? system. ?
> ? ?
> ? [ View full report ]
>
> Where I do see the error from the first screen again:
> Date: Tue Apr 7 16:59:08 2020
> DistroRelease: Ubuntu 20.04
> ExecutablePath: /snap/subiquity/1625/usr/bin/subiquity
> HookError_powerpc:
> Traceback (most recent call last):
> File
> "/snap/subiquity/1625/usr/lib/python3/dist-packages/apport/report.py", line
> 218, in _run_hook
> symb['add_info'](report, ui)
> File "/usr/share/apport/general-hooks/powerpc.py", line 42, in add_info
> is_kernel = report['ProblemType'].startswith('Kernel') or 'linux' in
> report.get('Package')
> TypeError: argument of type 'NoneType' is not iterable
>
> And also:
> KeyError: 'MAJOR'
> 2020-04-07 16:59:08,491 DEBUG subiquity.core:369 generating crash report
> 2020-04-07 16:59:08,492 INFO subiquity.core:386 saving crash report 'block
> prob
> ing crashed with KeyError' to
> /var/crash/1586278748.491911650.block_probe_fail.c
> rash
> 2020-04-07 16:59:08,492 DEBUG root:39 start:
> subiquity/Filesystem/_probe/probe_
> once: restricted=True
> 2020-04-07 16:59:08,492 DEBUG root:39 start:
> subiquity/Error/1586278748.4919116
> 50.block_probe_fail/add_info:
> 2020-04-07 16:59:08,519 DEBUG urllib3.connectionpool:396
> http://localhost:None
> "GET /v2/find?select=refresh HTTP/1.1" 200 59
> return fut.result()
> File
> "/snap/subiquity/1625/lib/python3.6/site-packages/subiquity/controllers/filesystem.py",
> line 119, in _probe_once
> self.app.prober.get_storage, probe_types)
> File
> "/snap/subiquity/1625/lib/python3.6/site-packages/subiquitycore/async_helpers.py",
> line 46, in run_in_thread
> return await loop.run_in_executor(None, func, *args)
> File
> "/snap/subiquity/1625/usr/lib/python3.6/concurrent/futures/thread.py", line
> 56, in run
> result = self.fn(*self.args, **self.kwargs)
> File
> "/snap/subiquity/1625/lib/python3.6/site-packages/subiquitycore/prober.py",
> line 60, in get_storage
> return Storage().probe(probe_types=probe_types)
>
> I did use the 'send to canonical'.
>
> The devices do appear at the shell, I can see the nvme using fdisk:
> Disk /dev/nvme0n1: 1.47 TiB, 1600321314816 bytes, 390703446 sectors
> Disk model: PCIe3 1.6TB NVMe Flash Adapter II x8
> Units: sectors of 1 * 4096 = 4096 bytes
> Sector size (logical/physical): 4096 bytes / 4096 bytes
> I/O size (minimum/optimal): 4096 bytes / 4096 bytes
> Disklabel type: gpt
> Disk identifier: 518B811D-B950-422D-9C29-7C31E82F9C82
>
> Device Start End Sectors Size Type
> /dev/nvme0n1p1 256 2047 1792 7M PowerPC PReP boot
> /dev/nvme0n1p2 2048 390703359 390701312 1.5T Linux filesystem
>
> Let me know if I should add additional logs here, or if you have access
> to them via the installer send to.
>
> --
> You received this bug notification because you are subscribed to Ubuntu.
> Matching subscriptions: architecture-ppc64le
> https://bugs.launchpad.net/bugs/1861655
>
> Title:
> [Ubu 20.04][kernel-5.4.0-12-generic][WSP-DD2.3] Unable to install Ubu
> 20.4 on NVMe disk
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu-power-systems/+bug/1861655/+subscriptions
>
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to grub-installer in Ubuntu.
https://bugs.launchpad.net/bugs/1861655
Title:
[Ubu 20.04][kernel-5.4.0-12-generic][WSP-DD2.3] Unable to install Ubu
20.4 on NVMe disk
Status in The Ubuntu-power-systems project:
Confirmed
Status in grub-installer package in Ubuntu:
Confirmed
Status in subiquity package in Ubuntu:
Confirmed
Bug description:
[Ubu 20.04][kernel-5.4.0-12-generic][WSP-DD2.3] Unable to install Ubu 20.4 on NVMe disk
Contact Information = kalshett at in.ibm.com, naveet89 at in.ibm.com, nasastry at in.ibm.com
---uname output---
[Ubu 20.04][kernel-5.4.0-12-generic]
Machine Type = Witherspoon DD2.3
Test Environment:
* Hardware: Witherspoon-DD2.3
* Ubuntu 20.04
* kernel: 5.4.0-12-generic #15-Ubuntu
Steps:
1. Kick start Ubu 20.4 on Witherspoon-DD2.3 baremetal
2. Select NVMe disk for installation, at the end of the install seen Grub boot loader issue
??????????????????????? Select and install software ???????????????????????
? ?
?? [!!] Install the GRUB boot loader on a hard disk ??
???????????? ? ?????????
? ? Unable to install GRUB in /dev/nvme0n1p1 ? ?
? ? Executing 'grub-install /dev/nvme0n1p1' failed. ? ?
? ? ? ?
? Running "? This is a fatal error. ? ?
? ? ? ?
???????????? <Go Back> <Continue> ? ?????????
? ?
??????????????????????????????????????????????????????
????????? [!!] Install the GRUB boot loader on a hard disk ??????????
? ?
? Installation step failed ?
? An installation step failed. You can try to run the failing item ?
? again from the menu, or skip it and choose something else. The ?
? failing step is: Install the GRUB boot loader on a hard disk ?
? ?
? <Continue> ?
? ?
?????????????????????????????????????????????????????????????????????
<Tab> moves; <Space> selects; <Enter> activates buttons
Complete install screenshot attached...
grub-install doesn't seem to install the bootloader on the nvme device.
--------------------------------------------------------------------------
Logs below -
Jan 31 16:01:51 in-target: Installing for powerpc-ieee1275 platform.^M
Jan 31 16:01:52 in-target: grub-install: error: unknown filesystem.^M
Jan 31 16:01:52 in-target: Failed: grub-install --target=powerpc-ieee1275 /dev/sda1 ^M
Jan 31 16:01:52 in-target: WARNING: Bootloader is not properly installed, system may not be bootable^M
..
..
Jan 31 16:01:57 40grub2: debug: parsing: fi
Jan 31 16:01:57 40grub2: debug: parsing: ### END /etc/grub.d/41_custom ###
Jan 31 16:01:57 50mounted-tests: debug: /usr/lib/linux-boot-probes/mounted/40grub2 succeeded
Jan 31 16:01:57 linux-boot-prober: debug: linux detected by /usr/lib/linux-boot-probes/50mounted-tests
Jan 31 16:01:57 grub-installer: info: Installing grub on '/dev/nvme0n1p1'
Jan 31 16:01:57 grub-installer: info: grub-install does not support --no-floppy
Jan 31 16:01:57 grub-installer: info: Running chroot /target grub-install --force "/dev/nvme0n1p1"
Jan 31 16:01:57 grub-installer: Installing for powerpc-ieee1275 platform.
Jan 31 16:01:58 grub-installer: grub-install: error: unknown filesystem.
Jan 31 16:01:58 grub-installer: error: Running 'grub-install --force "/dev/nvme0n1p1"' failed.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1861655/+subscriptions
More information about the foundations-bugs
mailing list