[Bug 1880869] Re: Use persistent device name for vdevs

[Launchpad Bug Tracker]

This bug was fixed in the package ubiquity - 20.04.15.1

---------------
ubiquity (20.04.15.1) focal; urgency=medium

  [ Sebastien Bacher ]
  * debian/real-po: updated translations from launchpad, including strings
    from the new subpage for RST (LP: #1874103)

  [ Michael Hudson-Doyle ]
  * make grub_default consider the boot argument in the non-removable case
    (LP: #1847898)

  [ Jean-Baptiste Lallement ]
  * Enable ZFS autotrim (LP: #1883686)
  * Use persistent path for pool's vdevs (LP: #1880869)
  * Do not export all pools (LP: #1875045)

  [ Dimitri John Ledkov ]
  * ubiquity-dm: start gsd-keyboard for keyboard indicator (LP: #1847307)

 -- Dimitri John Ledkov <xnox at ubuntu.com>  Tue, 16 Jun 2020 11:17:42
+0100

** Changed in: ubiquity (Ubuntu Focal)
       Status: Fix Committed => Fix Released

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

Title:
  Use persistent device name for vdevs

Status in ubiquity:
  Unknown
Status in ubiquity package in Ubuntu:
  Fix Released
Status in ubiquity source package in Focal:
  Fix Released

Bug description:
  [Impact]

   * ZFS pools were created with device names such as /dev/sdX,
  /dev/vdX,... However, these names are not stable and may change on
  each reboot, leading to an unbootable system.

   * "zpool create" now uses persistent device names with PARTUUID
  instead.

  [Test Case]

   * After a fresh installation run the following command:
  $ zpool status -P 
  Verify that the device is something like /dev/disk/by-partuuid/<some id>

  $ zpool status -PL
  Verify that the device is something like /dev/[s,v,h]dX and corresponds to the device selected during installation.

  
  [Regression Potential]

   * Likely low risk of regression. Worst case system doesn't boot after
  a fresh installation which is better than today because the system may
  boot but subsequent boots may not.

  [Other Info]

   * Already shipped in Groovy

  [Original Bug report]

  ZFS pools are currently created with device names such as /dev/sdX, /dev/vdX,... However, this name is not stable and may change on each reboot.
  "zpool create" must use persistent device names like UUID or PARTUUID instead.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.10
  Package: ubiquity (not installed)
  ProcVersionSignature: Ubuntu 5.4.0-18.22-generic 5.4.24
  Uname: Linux 5.4.0-18-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu36
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed May 27 13:52:13 2020
  InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper initrd=/casper/initrd.lz quiet splash -- keyboard-configuration/layoutcode=fr keyboard-configuration/variantcode=oss
  InstallationDate: Installed on 2014-07-15 (2143 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140520)
  SourcePackage: ubiquity
  UpgradeStatus: Upgraded to groovy on 2018-03-24 (794 days ago)

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