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

[Brian Murray]

Hello Jean-Baptiste, or anyone else affected,

Accepted ubiquity into focal-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/ubiquity/20.04.15.1 in
a few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
focal to verification-done-focal. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-focal. In either case, without details of your testing we will
not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

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

** Tags added: verification-needed verification-needed-focal

-- 
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 Committed

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