[Bug 1900274] Re: Ubiquity incorrectly states available storage when storage is hot-added during runtime

[Tom Reynolds]

Attaching screenshot previously stored at imgur.com

** Attachment added: "ubiquity_incorrect_fs_allocation_display.png"
   https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1900274/+attachment/5423474/+files/ubiquity_incorrect_fs_allocation_display.png

** Description changed:

  If storage is hot-added during installer runtime, this results in the
  installer incorrectly stating the amount of available storage.
  
  Steps to reproduce:
  I booted the Ubuntu 20.04.1 Desktop installer in a VM from a (virtual) CD-ROM drive, in BIOS mode. No other storage was attached to this VM at the time.
  I started the installed and proceeded to the step where it reported that only 0.0B of required 8.6GB are available to install Ubuntu on.
  I used the "back" button to return to the first installation screen.
  I attached a (virtual) HDD to the SATA bus of this VM, with a total capacity of 10 GB.
  I opened a terminal (Ctrl-Alt-T) and ran fdisk - it did not show this disk, yet.
  I used apt to install the sg3-utils package, and ran the rescan-scsi-bus.sh script it provides (as root).
  I used fdisk to create a GPT partition table on this disk, and used parted to verify it had been created. (The installer later overwrote this with an MBR partition table.)
  I switched back to the active installer, and proceeded through the installation screens, reaching the same message as before, reporting that only 0B of required 8.6GB (?) are available to install Ubuntu on. Contrary to my previous attempt, the "continue" button was now enabled, though:
  
- https://i.imgur.com/RKZPGLu.png
+ https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1900274/+attachment/5423474/+files/ubiquity_incorrect_fs_allocation_display.png
  
  I was able to continue and complete the installation without errors or
  warnings, and the system booted successfully.
  
  NB: The virtualization used is Virtualbox 6.1.14 r140239 (upstream
  packages) on an Ubuntu 18.04 LTS host.

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

Title:
  Ubiquity incorrectly states available storage when storage is hot-
  added during runtime

Status in ubiquity package in Ubuntu:
  New

Bug description:
  If storage is hot-added during installer runtime, this results in the
  installer incorrectly stating the amount of available storage.

  Steps to reproduce:
  I booted the Ubuntu 20.04.1 Desktop installer in a VM from a (virtual) CD-ROM drive, in BIOS mode. No other storage was attached to this VM at the time.
  I started the installed and proceeded to the step where it reported that only 0.0B of required 8.6GB are available to install Ubuntu on.
  I used the "back" button to return to the first installation screen.
  I attached a (virtual) HDD to the SATA bus of this VM, with a total capacity of 10 GB.
  I opened a terminal (Ctrl-Alt-T) and ran fdisk - it did not show this disk, yet.
  I used apt to install the sg3-utils package, and ran the rescan-scsi-bus.sh script it provides (as root).
  I used fdisk to create a GPT partition table on this disk, and used parted to verify it had been created. (The installer later overwrote this with an MBR partition table.)
  I switched back to the active installer, and proceeded through the installation screens, reaching the same message as before, reporting that only 0B of required 8.6GB (?) are available to install Ubuntu on. Contrary to my previous attempt, the "continue" button was now enabled, though:

  https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1900274/+attachment/5423474/+files/ubiquity_incorrect_fs_allocation_display.png

  I was able to continue and complete the installation without errors or
  warnings, and the system booted successfully.

  NB: The virtualization used is Virtualbox 6.1.14 r140239 (upstream
  packages) on an Ubuntu 18.04 LTS host.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1900274/+subscriptions