debcrafters-packages team mailing list archive

[Frank Heimes <2111695@xxxxxxxxxxxxxxxxxx>]

Okay, so esp. due to comment #4:
https://bugs.launchpad.net/ubuntu/+source/subiquity/+bug/2111695/comments/4
that even more makes me think that the order of enabling the DASD disk is not correct.

The autoinstall file is often generated with the help of an interactive installation.
And if one enabled in the installer text UI the DASD disks like this:
1. 0001 / dasda (mod 54)
2. 0002 / dasbb (mod 27)
but the the disks are enabled in the early_commands section of the autoinstall yaml file in a different order, like:
  early-commands:
  - chzdev dasd-eckd --enable 0002
  - chzdev dasd-eckd --enable 0001
And using an above autoinstall scheme
DASD 0002 will become dasda, now be the smaller disk and
DASD 0001 will become dasdb, now the bigger one
hence the disk geometry stored while the autoinstall was created does not fit anymore.

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

-- 
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