[Bug 2080474] Comment bridged from LTC Bugzilla

Thu Dec 4 10:11:27 UTC 2025

------- Comment From vajain21 at in.ibm.com 2025-12-04 05:03 EDT-------
(In reply to comment #117)
> Today I setup a system with two LUNs (could do more if needed), both are
> connected to their own pair of two HBAs, again each with 2 paths, and I
> could complete a default 25.10 installation on the first LUN (however, on a
> different architecture):
>
> $ sudo multipath -ll
> mpatha (3600507630bffd3d70000000000000005) dm-0 IBM,2107900
> size=96G features='1 queue_if_no_path' hwhandler='1 alua' wp=rw
> `-+- policy='service-time 0' prio=50 status=active
> |- 0:0:0:1074085888 sda 8:0  active ready running
> |- 0:0:1:1074085888 sdb 8:16 active ready running
> |- 1:0:0:1074085888 sdc 8:32 active ready running
> `- 1:0:1:1074085888 sdd 8:48 active ready running
> mpathb (3600507630bffd3d70000000000000107) dm-4 IBM,2107900
> size=96G features='1 queue_if_no_path' hwhandler='1 alua' wp=rw
> `-+- policy='service-time 0' prio=50 status=active
> |- 3:0:0:1074216961 sdg 8:96  active ready running
> |- 3:0:1:1074216961 sdh 8:112 active ready running
> |- 2:0:0:1074216961 sde 8:64  active ready running
> `- 2:0:1:1074216961 sdf 8:80  active ready running
>
> I installed the OS on the first LUN, but did nothing with the second.
>
> $ sudo dmsetup ls --tree
> mpatha-part1 (252:1)
> ??mpatha (252:0)
> ?? (8:48)
> ?? (8:32)
> ?? (8:16)
> ?? (8:0)
> mpathb (252:4)
> ?? (8:80)
> ?? (8:64)
> ?? (8:112)
> ?? (8:96)
> ubuntu--vg-ubuntu--lv (252:3)
> ??mpatha-part2 (252:2)
> ??mpatha (252:0)
> ?? (8:48)
> ?? (8:32)
> ?? (8:16)
> ?? (8:0)
>
> So I need to know more about your particular setup:
> # of HBAs
> # LUNs
> # paths
> # if you installed on just one LUN (and didn't touched the other during
> install)
> # or if you did an install across LUNs (parts of the filesystem on LUN #1
> and other parts on LUN #2)
> etc.
> to be able to recreate a system that is closer to your ...

Hi Canonical,

Discussion on the new bug has been moved to a new launchpad bug
https://bugs.launchpad.net/ubuntu/+source/debian-installer/+bug/2133480 which has the necessary details on the current recreate.

This bug will be closed once verified, as it was originally reported for
installation failure on system with single multipath which is fixed now.

~ Vaibhav

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

Title:
  ubuntu installation failing for systems having SAN disk

Status in subiquity:
  New
Status in The Ubuntu-power-systems project:
  In Progress
Status in multipath-tools package in Ubuntu:
  Fix Released
Status in subiquity package in Ubuntu:
  New

Bug description:
  == Comment: - Anushree Mathur ==
  OS: 24.04 LTS (Noble Numbat)
  I started the Ubuntu installation for 24.04 LTS (Noble Numbat) on L1(HOST) having SAN disk, it failed with the following error just after I chose the disk.

  Ubuntu 24.04 LTS ubuntu-server hvc0

  connecting...  
  waiting for cloud-init...  
  generating crash report
  report saved to /var/crash/1724388235.797082424.ui.crash
  Traceback (most recent call last):
    File "/snap/subiquity/5745/lib/python3.10/site-packages/subiquity/client/controllers/filesystem.py", line 273, in _guided_choice
      self.ui.set_body(FilesystemView(self.model, self))
    File "/snap/subiquity/5745/lib/python3.10/site-packages/subiquity/ui/views/filesystem/filesystem.py", line 485, in __init__
      self.refresh_model_inputs()
    File "/snap/subiquity/5745/lib/python3.10/site-packages/subiquity/ui/views/filesystem/filesystem.py", line 540, in refresh_model_inputs
      self.avail_list.refresh_model_inputs()
    File "/snap/subiquity/5745/lib/python3.10/site-packages/subiquity/ui/views/filesystem/filesystem.py", line 417, in refresh_model_inputs
      for obj, cells in summarize_device(device, filter):
    File "/snap/subiquity/5745/lib/python3.10/site-packages/subiquity/ui/views/filesystem/helpers.py", line 32, in summarize_device
      anns = labels.annotations(device) + labels.usage_labels(device)
    File "/snap/subiquity/5745/usr/lib/python3.10/functools.py", line 889, in wrapper
      return dispatch(args[0].__class__)(*args, **kw)
    File "/snap/subiquity/5745/lib/python3.10/site-packages/subiquity/common/filesystem/labels.py", line 100, in _annotations_vg
      member = next(iter(vg.devices))
  StopIteration

  The above exception was the direct cause of the following exception:

  Traceback (most recent call last):
    File "/snap/subiquity/5745/usr/bin/subiquity", line 8, in <module>
      sys.exit(main())
    File "/snap/subiquity/5745/lib/python3.10/site-packages/subiquity/cmd/tui.py", line 158, in main
      asyncio.run(run_with_loop())
    File "/snap/subiquity/5745/usr/lib/python3.10/asyncio/runners.py", line 44, in run
      return loop.run_until_complete(main)
    File "/snap/subiquity/5745/usr/lib/python3.10/asyncio/base_events.py", line 649, in run_until_complete
      return future.result()
    File "/snap/subiquity/5745/lib/python3.10/site-packages/subiquity/cmd/tui.py", line 156, in run_with_loop
      await subiquity_interface.run()
    File "/snap/subiquity/5745/lib/python3.10/site-packages/subiquity/client/client.py", line 403, in run
      await super().run()
    File "/snap/subiquity/5745/lib/python3.10/site-packages/subiquitycore/tui.py", line 351, in run
      await super().run()
    File "/snap/subiquity/5745/lib/python3.10/site-packages/subiquitycore/core.py", line 134, in run
      raise exc
  RuntimeError: coroutine raised StopIteration

  Ubuntu 24.04 LTS ubuntu-server hvc0

  connecting...  
  ProblemType: Bug
  Architecture: ppc64el
  CrashDB: {'impl': 'launchpad', 'project': 'subiquity'}

  I tried following 2 installation methods, it is failing in both the ways: 
  1) kexec method
  2) attaching vdvd and starting installer

  NOTE: It is happening only when the system has SAN disks otherwise this installation worked fine.
  I will be attaching the crash report for this!

  == Comment:- Hariharan T S ==
  Verified the following cases. 
  Installation on Disk from VIOS  - PASSED
  Installatoin on Disk from VIOS and system had Disks from SAN - FAILED
  Installation on Disk from SAN and system ahd Disk from VIOS - FAILED

  == Comment:- Vaibhav Jain ==
  Problem seems to happening when Subuquity enters the disk partition view. The system has a SAN disk and an existing Mullti Path DM volume on it.

  Mirroring to distro

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