[Bug 1893818] Re: Several blockprobe errors if trying to install the groovy daily live on LPAR

[Frank Heimes]

I can confirm that it's fixed with image:
http://cdimage.ubuntu.com/ubuntu-server/daily-live/20201014.1/groovy-live-server-s390x.iso 
I did two installations - on z/VM and on LPAR (both of course zFCP) - and the blockprobe issues no longer occurred.

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

Title:
  Several blockprobe errors if trying to install the groovy daily live
  on LPAR

Status in curtin:
  Confirmed
Status in subiquity:
  Triaged
Status in Ubuntu on IBM z Systems:
  Confirmed
Status in livecd-rootfs package in Ubuntu:
  Fix Released
Status in multipath-tools package in Ubuntu:
  Invalid
Status in probert package in Ubuntu:
  New

Bug description:
  If trying to do a zFCP installation with groovy daily live I run into
  these blockprobe errors:

  ┌────────────────────────────────────────────────────────────────────────┐
  │                                                                        │
  │  Sorry, there was a problem examining the storage devices on this   ▴  │
  │  system.                                                            █  │
  │                                                                     █  │
  │                       [ View full report      ]                     █  │
  │                                                                     █  │
  │  If you want to help improve the installer, you can send an error   █  │
  │  report.                                                            █  │
  │                                                                     █  │
  │                       [ Send to Canonical     ]                     █  │
  │                                                                     █  │
  │  You can continue and the installer will just present the disks     █  │
  │  present in the system and not other block devices, or you may be   █  │
  │  able to fix the issue by switching to a shell and reconfiguring the   │
  │  system's block devices manually.                                      │
  │                                                                     ▾  │
  │                                                                        │
  └────────────────────────────────────────────────────────────────────────┘

  2020-09-01 15:51:05,760 DEBUG subiquitycore.prober:35 Prober() init finished, data:None
   2020-09-01 15:51:05,761 DEBUG subiquitycore.core:97 KDGKBTYPE failed OSError(25, 'Inappropriate ioctl for device')
   2020-09-01 15:51:05,761 DEBUG asyncio:54 Using selector: EpollSelector
   2020-09-01 15:51:05,762 DEBUG subiquity.signals:50 connect_signal: network-proxy-set -> <function Subiquity.__init__.<locals>.<lambda> at 0x3ffa73e56a8>
   2020-09-01 15:51:05,762 DEBUG subiquity.signals:50 connect_signal: network-change -> Subiquity._network_change
   2020-09-01 15:51:05,762 DEBUG subiquitycore.core:643 Application.run
   2020-09-01 15:51:05,764 DEBUG curtin:89 Running command ['dpkg', '--print-architecture'] with allowed return codes [0] (capture=True)

  I've attached a tgz with /var/crash and /var/log content.

To manage notifications about this bug go to:
https://bugs.launchpad.net/curtin/+bug/1893818/+subscriptions