[Touch-packages] [Bug 1862846] Re: Crash and failure installing focal
** Tags removed: sts-sponsor-mfo
--
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:
Fix Released
Status in curtin package in Ubuntu:
Fix Released
Status in util-linux package in Ubuntu:
Fix Released
Status in curtin source package in Eoan:
Invalid
Status in util-linux source package in Eoan:
Fix Released
Status in curtin source package in Focal:
Fix Released
Status in util-linux source package in Focal:
Fix Released
Status in util-linux package in Debian:
Fix Released
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)
* $ lsblk -no RM /dev/sdb1 # partition in removable disk
* Expected output: 1 # removable media
* Current output: 0 # not removable media
[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
[Touch-packages] [Bug 1862846] Re: Crash and failure installing focal
** Changed in: subiquity
Status: New => Fix Released
--
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:
Fix Released
Status in curtin package in Ubuntu:
Fix Released
Status in util-linux package in Ubuntu:
Fix Released
Status in curtin source package in Eoan:
Invalid
Status in util-linux source package in Eoan:
Fix Released
Status in curtin source package in Focal:
Fix Released
Status in util-linux source package in Focal:
Fix Released
Status in util-linux package in Debian:
Fix Released
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)
* $ lsblk -no RM /dev/sdb1 # partition in removable disk
* Expected output: 1 # removable media
* Current output: 0 # not removable media
[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
[Touch-packages] [Bug 1862846] Re: Crash and failure installing focal
** Changed in: util-linux (Debian)
Status: Confirmed => Fix Released
--
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:
Fix Released
Status in curtin source package in Eoan:
Invalid
Status in util-linux source package in Eoan:
Fix Released
Status in curtin source package in Focal:
Fix Released
Status in util-linux source package in Focal:
Fix Released
Status in util-linux package in Debian:
Fix Released
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)
* $ lsblk -no RM /dev/sdb1 # partition in removable disk
* Expected output: 1 # removable media
* Current output: 0 # not removable media
[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
[Touch-packages] [Bug 1862846] Re: Crash and failure installing focal
** Changed in: util-linux (Debian)
Status: New => Confirmed
--
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:
Fix Released
Status in curtin source package in Eoan:
Invalid
Status in util-linux source package in Eoan:
Fix Released
Status in curtin source package in Focal:
Fix Released
Status in util-linux source package in Focal:
Fix Released
Status in util-linux package in Debian:
Confirmed
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)
* $ lsblk -no RM /dev/sdb1 # partition in removable disk
* Expected output: 1 # removable media
* Current output: 0 # not removable media
[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
[Touch-packages] [Bug 1862846] Re: Crash and failure installing focal
This bug was fixed in the package util-linux - 2.34-0.1ubuntu2.3
---
util-linux (2.34-0.1ubuntu2.3) eoan; urgency=medium
* d/p/lsblk-force-to-print-PKNAME-for-partition.patch: fix regression
that lsblk doesn't print PKNAME column for partitions (LP: #1862846)
-- Mauricio Faria de Oliveira Thu, 20 Feb 2020
11:13:53 -0300
** Changed in: util-linux (Ubuntu Eoan)
Status: Fix Committed => Fix Released
--
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:
Fix Released
Status in curtin source package in Eoan:
Invalid
Status in util-linux source package in Eoan:
Fix Released
Status in curtin source package in Focal:
Fix Released
Status in util-linux source package in Focal:
Fix Released
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)
* $ lsblk -no RM /dev/sdb1 # partition in removable disk
* Expected output: 1 # removable media
* Current output: 0 # not removable media
[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
[Touch-packages] [Bug 1862846] Re: Crash and failure installing focal
Hi Lukasz, thanks! Sure thing, I'll add it.
--
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:
Fix Released
Status in curtin source package in Eoan:
Invalid
Status in util-linux source package in Eoan:
Fix Committed
Status in curtin source package in Focal:
Fix Released
Status in util-linux source package in Focal:
Fix Released
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)
* $ lsblk -no RM /dev/sdb1 # partition in removable disk
* Expected output: 1 # removable media
* Current output: 0 # not removable media
[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
[Touch-packages] [Bug 1862846] Re: Crash and failure installing focal
$ lsb_release -cs
eoan
Test device: partition (sdb1) in removable / USB flash disk (sdb)
$ ls -1d /sys/block/sdb/sdb1
/sys/block/sdb/sdb1
$ cat /sys/block/sdb/removable
1
eoan-proposed:
---
- PKNAME shows partition's parent/wholedisk.
- RM shows 1 for removable disk's partition.
$ dpkg -s util-linux | grep ^Version:
Version: 2.34-0.1ubuntu2.3
$ lsblk -no PKNAME /dev/sdb1
sdb
$ lsblk -no RM /dev/sdb1
1
eoan-updates:
---
- PKNAME shows nothing.
- RM shows 0 despite it's actually a removable disk's partition.
$ dpkg -s util-linux | grep ^Version:
Version: 2.34-0.1ubuntu2.2
$ lsblk -no PKNAME /dev/sdb1
$
$ lsblk -no RM /dev/sdb1
0
** Description changed:
[Impact]
- * lsblk no longer prints a partition's parent
-kernel device name (the wholedisk).
-(i.e., 'lsblk -no PKNAME /dev/partition')
+ * 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')
+ * 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 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.
+ * 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
+ * $ lsblk -no PKNAME /dev/vda1 # partition
- * Expected output: vda # wholedisk
+ * Expected output: vda # wholedisk
- * Current output: (nothing)
+ * Current output: (nothing)
+
+ * $ lsblk -no RM /dev/sdb1 # partition in removable disk
+
+ * Expected output: 1 # removable media
+
+ * Current output: 0 # not removable media
[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.
+ * 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 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.
+ * 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
+ * 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.
** Tags added: verification-done-eoan
--
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:
Fix Released
Status in curtin source package in Eoan:
Invalid
Status in util-linux source package in Eoan:
Fix Committed
Status in curtin source package in Focal:
Fix Released
Status in util-linux source package in Focal:
Fix Released
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
[Touch-packages] [Bug 1862846] Re: Crash and failure installing focal
Hey! The package looks good so I'll accept it. In the impact you have
mentioned that currently lsblk -no RM also doesn't work correctly, so
maybe we should add it to the test case?
** Changed in: util-linux (Ubuntu Eoan)
Status: In Progress => Fix Committed
--
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:
Fix Released
Status in curtin source package in Eoan:
Invalid
Status in util-linux source package in Eoan:
Fix Committed
Status in curtin source package in Focal:
Fix Released
Status in util-linux source package in Focal:
Fix Released
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
[Touch-packages] [Bug 1862846] Re: Crash and failure installing focal
This bug was fixed in the package util-linux - 2.34-0.1ubuntu7
---
util-linux (2.34-0.1ubuntu7) focal; urgency=medium
* d/p/lsblk-force-to-print-PKNAME-for-partition.patch: fix regression
that lsblk doesn't print PKNAME column for partitions (LP: #1862846)
-- Mauricio Faria de Oliveira Thu, 20 Feb 2020
11:09:29 -0300
** Changed in: util-linux (Ubuntu Focal)
Status: In Progress => Fix Released
--
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:
Fix Released
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:
Fix Released
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
[Touch-packages] [Bug 1862846] Re: Crash and failure installing focal
@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
[Touch-packages] [Bug 1862846] Re: Crash and failure installing focal
util-linux uploaded in focal. Thanks Mauricio ! -- 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: 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
[Touch-packages] [Bug 1862846] Re: Crash and failure installing focal
** Tags removed: champagne -- 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: 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
[Touch-packages] [Bug 1862846] Re: Crash and failure installing focal
** Tags added: patch -- 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: 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
[Touch-packages] [Bug 1862846] Re: Crash and failure installing focal
** Tags added: sts-sponsor-mfo -- 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: 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
[Touch-packages] [Bug 1862846] Re: Crash and failure installing focal
** Patch added: "lp1862846_focal_util-linux.debdiff" https://bugs.launchpad.net/subiquity/+bug/1862846/+attachment/5329790/+files/lp1862846_focal_util-linux.debdiff -- 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: 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
[Touch-packages] [Bug 1862846] Re: Crash and failure installing focal
@ltrager, Indeed, I see the refactor in curtin. :) Absolutely agree w/ you, it's a regression in util-linux, and after following up with you on IRC yesterday that it is OK for me to submit the fix to Ubuntu, I worked on it. I've tested the patch today, and it's currently building on all architectures in a test PPA. If all goes well, it should move forward to Focal and Eoan in the coming days. Providing test steps in the next comment. Attaching the debdiffs for reference. cheers, Mauricio -- 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: 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
[Touch-packages] [Bug 1862846] Re: Crash and failure installing focal
util-linux / test steps === Bionic --- No regression: parent kernel device name $ dpkg -s util-linux | grep ^Version: Version: 2.31.1-0.4ubuntu3.5 $ lsblk -no pkname /dev/vda1 vda Eoan --- Before: empty string $ dpkg -s util-linux | grep ^Version: Version: 2.34-0.1ubuntu2.2 $ lsblk -no pkname /dev/vda1 $ After: parent kernel device name $ dpkg -s util-linux | grep ^Version: Version: 2.34-0.1ubuntu2.2+pkname1 $ lsblk -no pkname /dev/vda1 vda Focal --- Before: empty string $ dpkg -s util-linux | grep ^Version: Version: 2.34-0.1ubuntu6 $ lsblk -no pkname /dev/vda1 $ After: parent kernel device name $ dpkg -s util-linux | grep ^Version: Version: 2.34-0.1ubuntu6+pkname1 $ lsblk -no pkname /dev/vda1 vda -- 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: 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
[Touch-packages] [Bug 1862846] Re: Crash and failure installing focal
** Patch added: "lp1862846_eoan_util-linux.debdiff" https://bugs.launchpad.net/subiquity/+bug/1862846/+attachment/5329791/+files/lp1862846_eoan_util-linux.debdiff ** Changed in: util-linux (Ubuntu Eoan) Status: New => In Progress ** Changed in: util-linux (Ubuntu Eoan) Importance: Undecided => Medium ** Changed in: util-linux (Ubuntu Eoan) Assignee: (unassigned) => Mauricio Faria de Oliveira (mfo) ** Changed in: util-linux (Ubuntu Focal) Status: New => In Progress ** Changed in: util-linux (Ubuntu Focal) Importance: Undecided => Medium ** Changed in: util-linux (Ubuntu Focal) Assignee: (unassigned) => Mauricio Faria de Oliveira (mfo) -- 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: 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
[Touch-packages] [Bug 1862846] Re: Crash and failure installing focal
Ryan has updated Curtin to no longer require that util-linux feature. I do think it would be good to carry that patch in Ubuntu as it other users will be effected by that regression. -- 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: New Status in curtin source package in Eoan: Invalid Status in util-linux source package in Eoan: New Status in curtin source package in Focal: Fix Released Status in util-linux source package in Focal: New Status in util-linux package in Debian: New 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
[Touch-packages] [Bug 1862846] Re: Crash and failure installing focal
@ltrager I'd be happy to handle the patch for util-linux on Ubuntu E/F if that helps; just let me know. -- 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: New Status in curtin source package in Eoan: Invalid Status in util-linux source package in Eoan: New Status in curtin source package in Focal: Fix Released Status in util-linux source package in Focal: New Status in util-linux package in Debian: New 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
[Touch-packages] [Bug 1862846] Re: Crash and failure installing focal
This bug was fixed in the package curtin - 19.3-26-g82f23e3d-0ubuntu1 --- curtin (19.3-26-g82f23e3d-0ubuntu1) focal; urgency=medium * New upstream snapshot. - install-grub: refactor uefi partition/disk searching (LP: #1862846) - doc: update Canonical contributors URL [Paul Tobias] - block-discover: detect additional "extended" partition types in MBR (LP: #1861251) - vmtests: skip focal bcache tests due to kernel bug - net/deps.py: detect openvswitch cfg and install openvswitch packages - vmtest: collection of vmtest related fixes to make things triple green - clear-holders: umap the parent mpath to wipe the underlying partitions - vmtests: bump fixby date out and fix false positive when date passes (LP: #1855148) - vmtests: drop disco tests using a tool to automate the process -- Ryan Harper Thu, 13 Feb 2020 21:08:59 -0600 ** Changed in: curtin (Ubuntu Focal) Status: In Progress => Fix Released -- 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: New Status in curtin source package in Eoan: Invalid Status in util-linux source package in Eoan: New Status in curtin source package in Focal: Fix Released Status in util-linux source package in Focal: New Status in util-linux package in Debian: New 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
[Touch-packages] [Bug 1862846] Re: Crash and failure installing focal
This bug is fixed with commit 82f23e3d to curtin on branch master. To view that commit see the following URL: https://git.launchpad.net/curtin/commit/?id=82f23e3d -- 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: In Progress Status in util-linux package in Ubuntu: New Status in curtin source package in Eoan: Invalid Status in util-linux source package in Eoan: New Status in curtin source package in Focal: In Progress Status in util-linux source package in Focal: New Status in util-linux package in Debian: New 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
[Touch-packages] [Bug 1862846] Re: Crash and failure installing focal
** Tags removed: rls-ff-incoming -- 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: In Progress Status in util-linux package in Ubuntu: New Status in curtin source package in Eoan: Invalid Status in util-linux source package in Eoan: New Status in curtin source package in Focal: In Progress Status in util-linux source package in Focal: New Status in util-linux package in Debian: New 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
[Touch-packages] [Bug 1862846] Re: Crash and failure installing focal
** Changed in: curtin (Ubuntu Focal) Status: Triaged => In Progress ** Changed in: curtin (Ubuntu Focal) Assignee: (unassigned) => Ryan Harper (raharper) -- 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: In Progress Status in util-linux package in Ubuntu: New Status in curtin source package in Eoan: Invalid Status in util-linux source package in Eoan: New Status in curtin source package in Focal: In Progress Status in util-linux source package in Focal: New Status in util-linux package in Debian: New 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
[Touch-packages] [Bug 1862846] Re: Crash and failure installing focal
** Changed in: util-linux (Debian) Status: Unknown => New -- 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: Triaged Status in util-linux package in Ubuntu: New Status in curtin source package in Eoan: Invalid Status in util-linux source package in Eoan: New Status in curtin source package in Focal: Triaged Status in util-linux source package in Focal: New Status in util-linux package in Debian: New 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
[Touch-packages] [Bug 1862846] Re: Crash and failure installing focal
** Merge proposal linked: https://code.launchpad.net/~raharper/curtin/+git/curtin/+merge/379024 -- 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: Triaged Status in util-linux package in Ubuntu: New Status in curtin source package in Eoan: Invalid Status in util-linux source package in Eoan: New Status in curtin source package in Focal: Triaged Status in util-linux source package in Focal: New Status in util-linux package in Debian: Unknown 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
[Touch-packages] [Bug 1862846] Re: Crash and failure installing focal
** Bug watch added: Debian Bug tracker #951217 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=951217 ** Also affects: util-linux (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=951217 Importance: Unknown Status: Unknown -- 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: Triaged Status in util-linux package in Ubuntu: New Status in curtin source package in Eoan: Invalid Status in util-linux source package in Eoan: New Status in curtin source package in Focal: Triaged Status in util-linux source package in Focal: New Status in util-linux package in Debian: Unknown 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
[Touch-packages] [Bug 1862846] Re: Crash and failure installing focal
@Alberto > I thought the installer would work similarly to what the desktop installer > does with btrfs, where it creates subvolumes for / and /home in the root > partition (as @ and @home). > > On my desktop, when I upgrade I just move @ out of the way (by renaming it) > and the installer creates a new one. > This is kinda nice as you can easily keep/revert to the old rootfs by > just changing which subvol is mounted at boot. Subiquity/curtin does not have support for btrfs subvolumes. -- 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: Triaged Status in util-linux package in Ubuntu: New Status in curtin source package in Eoan: Invalid Status in util-linux source package in Eoan: New Status in curtin source package in Focal: Triaged Status in util-linux source package in Focal: New 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
[Touch-packages] [Bug 1862846] Re: Crash and failure installing focal
@Lee Thanks for tracking down the util-linux bug. Since this is broken in 2.34 (eoan/focal); I'm thinking we should use sysfs to find the parent via device name walking; Given a kname (nvme0n1p1) of the target partition # look up sysfs path from kname % realpath /sys/class/block/nvme0n1p1 /sys/devices/pci:00/:00:02.0/:05:00.0/nvme/nvme0/nvme0n1/nvme0n1p1 # check if it's a partition % ls -al /sys/devices/pci:00/:00:02.0/:05:00.0/nvme/nvme0/nvme0n1/nvme0n1p1/partition -r--r--r-- 1 root root 4096 Feb 12 08:08 /sys/devices/pci:00/:00:02.0/:05:00.0/nvme/nvme0/nvme0n1/nvme0n1p1/partition # extract parent device path % dirname /sys/devices/pci:00/:00:02.0/:05:00.0/nvme/nvme0/nvme0n1/nvme0n1p1 /sys/devices/pci:00/:00:02.0/:05:00.0/nvme/nvme0/nvme0n1 # extract parent device major/minor % cat /sys/devices/pci:00/:00:02.0/:05:00.0/nvme/nvme0/nvme0n1/dev 259:0 # udev symlinks/dev/block/$MAJOR:$MINOR % ls -al /dev/block/259:0 lrwxrwxrwx 1 root root 10 Jan 18 00:16 /dev/block/259:0 -> ../nvme0n1 % realpath /dev/block/259:0 /dev/nvme0n1 -- 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: Triaged Status in util-linux package in Ubuntu: New Status in curtin source package in Eoan: Invalid Status in util-linux source package in Eoan: New Status in curtin source package in Focal: Triaged Status in util-linux source package in Focal: New 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
[Touch-packages] [Bug 1862846] Re: Crash and failure installing focal
** Also affects: util-linux (Ubuntu) Importance: Undecided Status: New ** Tags added: rls-ff-incoming ** Also affects: util-linux (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: curtin (Ubuntu Focal) Importance: High Status: Triaged ** Also affects: util-linux (Ubuntu Eoan) Importance: Undecided Status: New ** Also affects: curtin (Ubuntu Eoan) Importance: Undecided Status: New ** Changed in: curtin (Ubuntu Eoan) Status: New => Invalid -- 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: Triaged Status in util-linux package in Ubuntu: New Status in curtin source package in Eoan: Invalid Status in util-linux source package in Eoan: New Status in curtin source package in Focal: Triaged Status in util-linux source package in Focal: New 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
