subiquity probe_once fails with Invalid dep_id during 20.10 install
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Ubuntu on IBM z Systems |
Triaged
|
Critical
|
Canonical Foundations Team | ||
curtin |
New
|
Undecided
|
Unassigned | ||
subiquity |
New
|
Undecided
|
Unassigned |
Bug Description
While performing an install to a zVM guest using the 20.10 iso from October 1, the subiquity installer reports:
┌───
│ │
│ 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. │
│ ▾ │
│ │
└───
This happens just after enabling storage devices, from the installer ssh session. The inputs leading up to this failure on the SolutionsQA s5lp1-gen02 guest were:
English
dasd-eckd --> 0.0.0200 --> enable
zfcp-host --> 0.0.f201 --> enable
zfcp-host --> 0.0.f301 --> enable
Upon further inspection of the subiquity-debug.log (see attached) the following traceback is present:
2020-10-08 17:50:09,335 ERROR root:39 finish: subiquity/
2020-10-08 17:50:09,336 ERROR block-discover:161 block probing failed restricted=False
Traceback (most recent call last):
File "/snap/
await asyncio.
File "/snap/
return fut.result()
File "/snap/
return await meth(self, **kw)
File "/snap/
self.
File "/snap/
self.reset()
File "/snap/
self.
File "/snap/
tree = get_config_
File "/snap/
for dep in find_item_
File "/snap/
_validate_
File "/snap/
'Invalid dep_id (%s) not in storage config' % dep_id)
ValueError: Invalid dep_id (partition-sda1) not in storage config
2020-10-08 17:50:09,336 DEBUG subiquitycore.
2020-10-08 17:50:09,336 INFO subiquitycore.
The entire content of /var/log is attached, which includes the crash file mentioned just above.
In case you still have the system in place, would you mind also having a look /var/crash and if it's not empty (what I assume) attaching the content here, too?
(With "F2"
I think that if you scroll down the subiquity screen a bit, there will be an option to 'Continue' available - if so, are you able to complete the installation then?
I 'think' this could be a duplicate of LP 1893818, which happens to me mainly on LPARs, but at least on zFCP/SCSI multipath installations only. Filesystem/ _probe/ probe_once: FAIL: Invalid dep_id (partition-sda1) not in storage config"
There is the same log entry in subiquity-debug visible:
"2020-09-17 13:42:57,730 ERROR root:39 finish: subiquity/
But I'm waiting for an answer before I really mark this as duplicate ...