[Bug 2097613] Re: (auto-)Install issue with 25.04 on s390x using DASD disks

[Boris Barth]

=== Comment by Jan H. <IBM>  (copied&pasted manually as the mirroring
from IBM bugzilla <-> Canonical LP currently doesn't seem to work) ====

Responding to comment 7 [1] specifically in regards to the order of
device processing:

The order of processing when multiple devices are specified on the command line
is determined by implementation details of zdev device selection. It is deterministic,
but not directly related to the order in which devices are specified. While we
understand the convenience that this could bring to some users, but from a quick
look at the source, this would require quite some effort to implement. We'll note
this as an enhancement idea but cannot give an outlook if, and when this might be
implemented.

[1] https://bugs.launchpad.net/subiquity/+bug/2097613/comments/7

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

Title:
  (auto-)Install issue with 25.04 on s390x using DASD disks

Status in subiquity:
  Invalid
Status in Ubuntu on IBM z Systems:
  In Progress
Status in s390-tools package in Ubuntu:
  Confirmed

Bug description:
  This is actually a spin off of comment #9 of LP bug #2093352 "autoinstall crash with Ubuntu Server 25.04":
  https://bugs.launchpad.net/subiquity/+bug/2093352/comments/9
  since it's believed that this is a different bug compared to what's described as well.


  That's weird having done the same with an LPAR system now, using DASD disks (which I assumed to work), autoinstall fails on LPAR with:
  "
  2025-02-03 15:28:22,913 INFO probert.lvm:119 b' 1 logical volume(s) in volume group "s1lp15vg" now active\n'
  2025-01-31 15:28:25,619 INFO curtin:1396 Validating extracted storage config components
  2025-01-31 15:28:36,199 INFO root:38 finish: subiquity/Network/apply_config: SUCCESS: silent=False
  2025-01-31 15:28:46,210 ERROR root:38 finish: subiquity/Mirror/apply_autoinstall_config/waiting: FAIL:
  2025-01-31 15:29:00,731 ERROR root:38 finish: subiquity/Filesystem/apply_autoinstall_config/convert_autoinstall_config: FAIL: '/dev/dasda2'
  2025-01-31 15:29:00,731 ERROR root:38 finish: subiquity/Filesystem/apply_autoinstall_config: FAIL: '/dev/dasda2'
  2025-01-31 15:29:00,731 ERROR root:38 finish: subiquity/apply_autoinstall_config: FAIL: '/dev/dasda2'
  2025-01-31 15:29:00,731 ERROR subiquity.server.server:525 top level error
  Traceback (most recent call last):
    File "/snap/subiquity/6390/lib/python3.12/site-packages/subiquity/server/server.py", line 1043, in start
      await self.apply_autoinstall_config()
    File "/snap/subiquity/6390/lib/python3.12/site-packages/subiquitycore/context.py", line 165, in decorated_async
      return await meth(self, **kw)
             ^^^^^^^^^^^^^^^^^^^^^^
  "

  Looks like the device "/dev/dasda2" cannot be properly handled - but
  this is a proper partition on a DASD disk.

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