debcrafters-packages team mailing list archive

[bugproxy <2111695@xxxxxxxxxxxxxxxxxx>]

------- Comment on attachment From Andre.Wild4@xxxxxxx 2025-05-26 10:51 EDT-------


> And was the autoinstall done on LPAR or in z/VM?

Installation was done on LPAR

> I'm wondering if the DASD disks were always added/enabled in the same
order?

The order in the subiquity file is always the same.

> The order of how the disks are enabled need to always stay the same.

We're not really in control of that order I think.

As you can see in "subiquity-partitioning.conf" it uses /dev/dasdx path
to identify the dasd and that is causing all the issues. The proper path
would be "/dev/disk/by-path/ccw-0.0.d284" and so on. I haven't defined
that in the autoinstall file because I'm simply not aware of that
assignment that is done by the kernel.

** Attachment added: "Requested folders /var/log/installer and /var/crash"
   https://bugs.launchpad.net/bugs/2111695/+attachment/5880351/+files/ubuntu-installer-logs.tgz

-- 
You received this bug notification because you are a member of
Debcrafters packages, which is subscribed to curtin in Ubuntu.
https://bugs.launchpad.net/bugs/2111695

Title:
  [Ubuntu24.04] - curtin - subiquity installation with multiple dasd
  sizes leads to an error in partitioning

Status in Ubuntu on IBM z Systems:
  Triaged
Status in curtin package in Ubuntu:
  New
Status in subiquity package in Ubuntu:
  New

Bug description:
  Description:

  Automated installation of Ubuntu 24.04 on LPAR with
  subiquity/cloudinit fails because of wrong dasd partition size.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/2111695/+subscriptions