Ubuntu
subiquity package

  1. Bug #2009141
  2. Comment #46

Comment 46 for bug 2009141

Revision history for this message
bugproxy (bugproxy) wrote : Comment bridged from LTC Bugzilla

------- Comment From <email address hidden> 2023-04-19 19:54 EDT-------
(In reply to comment #41)
> You mentioned that

>wiping the LUNs for the OS itself and only enable this OS LUN during installation.

The 2 new OS LUNs (initial 22.04.1 lun and second lun for retest on 22.04.2) were new luns created on the storage and mapped to the host, so had no prior LVM configs.

Most likely the installer is having issues with the older OS 20.04.5 LUN, with an existing LVM config and used for ongoing tests and/or support

Current config with LVM configs include the following 3 OS luns

(A) 20.04.5 LTS (Focal Fossa) 50G Lun 360050762198c1fc2180000000b000132 - Legacy
(B) 22.04.1 LTS (Jammy Jellyfish) 100G Lun 36005076306ffd6d3000000000000014a - Currently booted
(C) 22.04.2 target install 102G Lun 36005076306ffd6d30000000000000143 - Test 22.04.2 install

I will next use the work-around to unmap all other OS luns with LVM configs from this host on the storage, in order to have a single OS lun discovered at install [i.e. for 20.04.2) and avoid the installer filling up /var/crash with crash files, returning "OSError: [Errno 28] No space left on device" after running out of space.

The expectation is to not have to unmap other OS luns with LVM configs from a host, in order for a single OS lun be discovered for an install to be successful

>Any additional LUNs can be easily added post-install and should not be enabled at install time (here, for testing and to be on the safe side).

The capability to install a new OS to a new lun, while older OS luns (used for testing/support) with LVM configs remain attached used to work.
Config B) 22.04.1 was installed, enabling zfcp 120d/130d with Config (A) OS lun already attached [however had to not enable zfcp 100d/110d for that install, otherwise hit "OSError: [Errno 28] No space left on device"]

Reducing config to having a single OS lun discovered at install, seems to be a take away in functionality

>Any additional LUNs can be easily added post-install and should not be enabled at >install time (here, for testing and to be on the safe side).
> (I think that's easier compared to disabling them on the SAN side ...)

This adds an additional step, while also requiring to update the initramfs and reboot, if the updated configuration needs to be persistent across follow-on reboots