[Bug 1897173] Re: 20.10 Installer crashes with partitions being written but unable to inform kernel of the change

[Norbert]

Currently all testcases about UM installation fail with symptoms:

GUI:

```
ERROR!!! (as superuser)

Partition(s) 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17,
18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31, 32, 33, 34, 35,
36, 37, 38, 39, 40, 41, 42, 43, 44, 45, 46, 47, 48, 49, 50, 51, 52, 53,
54, 55, 56, 57, 58, 59, 60, 61, 62, 63, 64, 65, 66, 67, 68, 69, 70, 71,
72, 73, 74, 75, 76, 77, 78, 79, 80, 81, 82, 83, 84, 85, 86, 87, 88, 89,
90, 91, 92, 93, 94, 95, 96, 97, 98, 99, 100, 101, 102, 103, 104, 105,
106, 107, 108, 109, 110, 111, 112, 113, 114, 115, 116, 117, 118, 119,
120, 121, 122, 123, 124, 125, 126, 127, 128 on /dev/vda have been
written, but we have been unable to inform the kernel of the change,
probably because it/they are in use. As a result, the old partition(s)
will remain in use. You should reboot now before making further changes.

[Ignore] [Cancel]
```

/var/log/partman , using QuickEMU

```
artman:parted_server: OUT: yes
partman:parted_server: Closing infifo and outfifo
partman:parted_server: main_loop: iteration 146
partman:parted_server: Opening infifo
partman:/lib/partman/commit.d/30parted: IN: COMMIT =dev=vda
partman:parted_server: Read command: COMMIT
partman:parted_server: command_commit()
partman:parted_server: Opening outfifo
partman:parted_server: command_commit: wiping superblocks from /dev/vda
partman:parted_server: do_wipe open(/dev/vda), 6
partman:parted_server: wiping superblocks from /dev/vda succeeded
partman:parted_server: OUT: Error
partman:/lib/partman/commit.d/30parted: error_handler: exception with type Error
partman:/lib/partman/commit.d/30parted: error_handler: reading message
partman:parted_server: OUT: Partition(s) 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31, 32, 33, 34, 35, 36, 37, 38, 39, 40, 41, 42, 43, 44, 45, 46, 47, 48, 49, 50, 51, 52, 53, 54, 55, 56, 57, 58, 59, 60, 61, 62, 63, 64, 65, 66, 67, 68, 69, 70, 71, 72, 73, 74, 75, 76, 77, 78, 79, 80, 81, 82, 83, 84, 85, 86, 87, 88, 89, 90, 91, 92, 93, 94, 95, 96, 97, 98, 99, 100, 101, 102, 103, 104, 105, 106, 107, 108, 109, 110, 111, 112, 113, 114, 115, 116, 117, 118, 119, 120, 121, 122, 123, 124, 125, 126, 127, 128 on /dev/vda have been written, but we have been unable to inform the kernel of the change, probably because it/they are in use.  As a result, the old partition(s) will remain in use.  You should reboot now before making further changes.
partman:parted_server: OUT: 
partman:parted_server: OUT: Ignore
partman:parted_server: OUT: Cancel
partman:parted_server: OUT: 

```

Using VirtualBox changes `/dev/vda` to `/dev/sda` and fails in the same
way.

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

Title:
  20.10 Installer crashes with partitions being written but unable to
  inform kernel of the change

Status in parted package in Ubuntu:
  Confirmed
Status in ubiquity package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu MATE currently daily 20.10 20200924 using QEMU.

  Expected outcome:
  Boot daily iso
  Choose Erase disk and install Ubuntu MATE
  Complete installation.

  Actual outcome:
  Boot daily iso
  Choose Erase disk and install Ubuntu MATE
  Install crashes with ERROR!!! (as superuser) Partition(s) on /dev/vda have been written, but we have been unable to inform the kernel of the change, probably because it/they are in use. As a result, the old partition(s) will remain in use. You should reboot now before making further changes.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: ubiquity 20.10.10
  ProcVersionSignature: Ubuntu 5.8.0-19.20-generic 5.8.8
  Uname: Linux 5.8.0-19-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu47
  Architecture: amd64
  CasperMD5CheckMismatches: ./casper/filesystem.squashfs
  CasperMD5CheckResult: skip
  CasperVersion: 1.452
  CurrentDesktop: MATE
  Date: Thu Sep 24 19:29:19 2020
  InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu-mate.seed maybe-ubiquity quiet splash ---
  LiveMediaBuild: Ubuntu-MATE 20.10 "Groovy Gorilla" - Alpha amd64 (20200924)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=<set>
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubiquity
  UpgradeStatus: No upgrade log present (probably fresh install)

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