@slashd, thanks for uploading util-linux to Focal.
I've added the SRU template and uploaded to Eoan.

** Description changed:

+ [Impact]
+ 
+  * lsblk no longer prints a partition's parent 
+    kernel device name (the wholedisk).
+    (i.e., 'lsblk -no PKNAME /dev/partition')
+ 
+  * Another impact is the 'removable media' check
+    always return zero for partitions.
+    (i.e., 'lsblk -no RM /dev/partition')
+ 
+  * The regression was introduced on v2.34, only
+    Eoan (v2.34) and later are affected.
+    Disco (v2.33) and earlier are not affected.
+ 
+  * The regression is fixed in v2.35, in commit
+    e3bb9bfb76c1 ("lsblk: force to print PKNAME
+    for partition"); fixes RM for partition too.
+ 
+ [Test Case]
+ 
+  * lsblk -no PKNAME /dev/vda1 # partition
+ 
+  * Expected output: vda # wholedisk
+ 
+  * Current output: (nothing)
+ 
+ [Regression Potential]
+ 
+  * Columns that depend on a partition device's
+    parent device (i.e., seen as 'wholedisk')
+    could in theory show incorrect values if
+    another bug is present in v2.34 for that.
+ 
+  * Other usages of 'parent' pointer in the
+    function have been examined and reported
+    (e.g. issue w/ removable media column),
+    and others found to not have issues
+    (e.g. --merge option, to group multiple
+    parents of a device, as in RAID.)
+    
+ [Other Info]
+ 
+  * The impacts to the curtin source package
+    have been addressed in other way, it no
+    longer requires util-linux, comment #14.
+ 
+  * util-linux github issue:
+    https://github.com/karelzak/util-linux/issues/813
+ 
+ [Original Bug Description]
+ 
  During an install of the daily live image for 20.04 Ubuntu Server, the
  installer first crashed and restarted itself, then failed to install the
  system.
  
  Attached are the logs left on the install USB key.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to util-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1862846

Title:
  Crash and failure installing focal

Status in subiquity:
  New
Status in curtin package in Ubuntu:
  Fix Released
Status in util-linux package in Ubuntu:
  In Progress
Status in curtin source package in Eoan:
  Invalid
Status in util-linux source package in Eoan:
  In Progress
Status in curtin source package in Focal:
  Fix Released
Status in util-linux source package in Focal:
  In Progress
Status in util-linux package in Debian:
  New

Bug description:
  [Impact]

   * lsblk no longer prints a partition's parent 
     kernel device name (the wholedisk).
     (i.e., 'lsblk -no PKNAME /dev/partition')

   * Another impact is the 'removable media' check
     always return zero for partitions.
     (i.e., 'lsblk -no RM /dev/partition')

   * The regression was introduced on v2.34, only
     Eoan (v2.34) and later are affected.
     Disco (v2.33) and earlier are not affected.

   * The regression is fixed in v2.35, in commit
     e3bb9bfb76c1 ("lsblk: force to print PKNAME
     for partition"); fixes RM for partition too.

  [Test Case]

   * lsblk -no PKNAME /dev/vda1 # partition

   * Expected output: vda # wholedisk

   * Current output: (nothing)

  [Regression Potential]

   * Columns that depend on a partition device's
     parent device (i.e., seen as 'wholedisk')
     could in theory show incorrect values if
     another bug is present in v2.34 for that.

   * Other usages of 'parent' pointer in the
     function have been examined and reported
     (e.g. issue w/ removable media column),
     and others found to not have issues
     (e.g. --merge option, to group multiple
     parents of a device, as in RAID.)
     
  [Other Info]

   * The impacts to the curtin source package
     have been addressed in other way, it no
     longer requires util-linux, comment #14.

   * util-linux github issue:
     https://github.com/karelzak/util-linux/issues/813

  [Original Bug Description]

  During an install of the daily live image for 20.04 Ubuntu Server, the
  installer first crashed and restarted itself, then failed to install
  the system.

  Attached are the logs left on the install USB key.

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

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to     : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to