[Kernel-packages] [Bug 1990621] Re: [SRU] PXE Boot contains wrong suggested link to ISO for live file system
** Tags removed: foundations-todo
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1990621
Title:
[SRU] PXE Boot contains wrong suggested link to ISO for live file
system
Status in casper package in Ubuntu:
Fix Released
Status in linux package in Ubuntu:
Invalid
Status in casper source package in Jammy:
Fix Committed
Status in linux source package in Jammy:
Invalid
Bug description:
[ Impact ]
* What are the effects of the bug on users?
casper's intercative netmount fails to download the latest
Ubuntu LTS ISOs after the release of the first point release
(e.g. 22.04.1)
* What is the justification for backporting the fix to the
There are at least 2 bug reports about this problem
(LP: #1990621, #1948884) and this fix will improve the
user experience with a low probaility of side effects.
* How does the upload fix the bug?
- The patch adds a '-latest' to the download URLs (see more
details here:
https://git.launchpad.net/casper/diff/scripts/casper?id=5075686ba44c942e58c71d2c99076fe72fe64022).
- Additionaly Łukasz Zemczak (sil2100) created symlinks that
(as the name of the urls imply) always points to the latest
Ubuntu ISO for a given version.
[ Test Plan ]
* How to reproduce the bug?
- Just run the failling parts of the casper script on a
22.04.1 <= x < 22.10 machine:
# would normally be set by initramfs-tools
$ DPKG_ARCH=amd64
# sets UBUNTU_CODENAME=jammy and VERSION_ID="22.04"
$ source /etc/os-release
# see
https://git.launchpad.net/casper/tree/scripts/casper?id=eb5ef85cb33fba28f9ae6e8da6194aaa521d5a49#n388
$
server_url=https://releases.ubuntu.com/$UBUNTU_CODENAME/ubuntu-$VERSION_ID-live-server-$DPKG_ARCH.iso
# see
https://git.launchpad.net/casper/tree/scripts/casper?id=eb5ef85cb33fba28f9ae6e8da6194aaa521d5a49#n267
$ wget "${server_url}" -O /dev/null
# You should observe an ERROR 404: Not Found.
* Test that the new links work:
- Test Script:
https://gist.github.com/dviererbe/0255733d25a27c9a3ddc0bfc9535c243
- New -latest URLs
-
https://releases.ubuntu.com/jammy/ubuntu-22.04-latest-live-server-amd64.iso
- https://releases.ubuntu.com/jammy/ubuntu-22.04-latest-desktop-amd64.iso
-
http://cdimage.ubuntu.com/releases/jammy/release/ubuntu-22.04-latest-live-server-arm64.iso
-
http://cdimage.ubuntu.com/releases/jammy/release/ubuntu-22.04-latest-live-server-ppc64el.iso
-
http://cdimage.ubuntu.com/releases/jammy/release/ubuntu-22.04-latest-live-server-s390x.iso
* Łukasz Zemczak (sil2100) tested that casper can handle
HTTP 301 redirects. (See
https://code.launchpad.net/~dviererbe/casper/+git/casper/+merge/446497/comments/1193559)
[ Where problems could occur ]
* The Ubuntu Release Team could forget or the automation
could stop working to update the -latest links, but this
would, in the worst case, result in a not more worse
situation than the current bug.
[ Other Info ]
* Nick Rosbrook (enr0n) pointed out in comment #3 that the
script allows the user to provide their own url.
This should only be considered a temporary workaround as
a user has to be aware of this bug and has to aquire a
URL by themself. Copy & pasting URLs from the web is
potentialy error prone and unsafe.
* As far as I am aware, there was a discussion between
Łukasz Zemczak (sil2100), Brian Murray (brian-murray) and
Steve Langasek (~vorlon) about the link namining. Neither
was particularly happy about the current solution, but no
better solution was found.
* Original Bug report:
When PXE booting without pulling in squashfs correctly the system
tried to be helpful (:-) and grab an ISO. The 22.04.1 Jammy release
contains a link to the old version which is not present anymore.
---
Unable to find a medium containing a live file system
Attempt interactive netboot from a URL?
yes no (default yes):
Two methods available for IP configuration:
* static: for static IP configuration
* dhcp: for automatic IP configuration
static dhcp (default 'dhcp'):
vlan id (optional):
https://releases.ubuntu.com/jammy/ubuntu-22.04-live-server-amd64.iso
(default)
https://releases.ubuntu.com/jammy/ubuntu-22.04-desktop-amd64.iso
url:
http_proxy (optional):
[ 125.454385] igb :00:14.0 eno1: igb: eno1 NIC Link is Up 1000 Mbps Full
Duplex, Flow Control: RX/TX
[ 125.566067] IPv6: ADDRCONF(NETDEV_CHANGE): eno1: link becomes ready
Begin: Trying netboot from 10.0.~.1: ... Begin: Trying to download and mount
https://releases.ubuntu.com/jammy/ubuntu-22.04-live-server-amd64.iso ...
BusyBox v1.30.1 (Ubuntu 1:1.30.1-7ubuntu3) built-in shell (ash)
Enter 'help' for a list of built-in commands.
[Kernel-packages] [Bug 1990621] Re: [SRU] PXE Boot contains wrong suggested link to ISO for live file system
** Description changed:
[ Impact ]
- * What are the effects of the bug on users?
-casper's intercative netmount fails to download the latest
-Ubuntu LTS ISOs after the release of the first point release
-(e.g. 22.04.1)
+ * What are the effects of the bug on users?
+ casper's intercative netmount fails to download the latest
+ Ubuntu LTS ISOs after the release of the first point release
+ (e.g. 22.04.1)
- * What is the justification for backporting the fix to the
-There are at least 2 bug reports about this problem
-(LP: #1990621, #1948884) and this fix will improve the
-user experience with a low probaility of side effects.
+ * What is the justification for backporting the fix to the
+ There are at least 2 bug reports about this problem
+ (LP: #1990621, #1948884) and this fix will improve the
+ user experience with a low probaility of side effects.
- * How does the upload fix the bug?
-
-- The patch adds a '-latest' to the download URLs (see more
- details here:
https://git.launchpad.net/casper/diff/scripts/casper?id=5075686ba44c942e58c71d2c99076fe72fe64022).
-- Additionaly Łukasz Zemczak (sil2100) created symlinks that
- (as the name of the urls imply) always points to the latest
- Ubuntu ISO for a given version.
+ * How does the upload fix the bug?
+
+ - The patch adds a '-latest' to the download URLs (see more
+ details here:
https://git.launchpad.net/casper/diff/scripts/casper?id=5075686ba44c942e58c71d2c99076fe72fe64022).
+ - Additionaly Łukasz Zemczak (sil2100) created symlinks that
+ (as the name of the urls imply) always points to the latest
+ Ubuntu ISO for a given version.
[ Test Plan ]
- * How to reproduce the bug?
+ * How to reproduce the bug?
-- Just run the failling parts of the casper script on a
- 22.04.1 <= x < 22.10 machine:
-
- # would normally be set by initramfs-tools
- $ DPKG_ARCH=amd64
+ - Just run the failling parts of the casper script on a
+ 22.04.1 <= x < 22.10 machine:
- # sets UBUNTU_CODENAME=jammy and VERSION_ID="22.04"
- $ source /etc/os-release
+ # would normally be set by initramfs-tools
+ $ DPKG_ARCH=amd64
- # see
https://git.launchpad.net/casper/tree/scripts/casper?id=eb5ef85cb33fba28f9ae6e8da6194aaa521d5a49#n388
- $
server_url=https://releases.ubuntu.com/$UBUNTU_CODENAME/ubuntu-$VERSION_ID-live-server-$DPKG_ARCH.iso
-
- # see
https://git.launchpad.net/casper/tree/scripts/casper?id=eb5ef85cb33fba28f9ae6e8da6194aaa521d5a49#n267
- $ wget "${server_url}" -O /dev/null
+ # sets UBUNTU_CODENAME=jammy and VERSION_ID="22.04"
+ $ source /etc/os-release
- # You should observe an ERROR 404: Not Found.
+ # see
https://git.launchpad.net/casper/tree/scripts/casper?id=eb5ef85cb33fba28f9ae6e8da6194aaa521d5a49#n388
+ $
server_url=https://releases.ubuntu.com/$UBUNTU_CODENAME/ubuntu-$VERSION_ID-live-server-$DPKG_ARCH.iso
- * Test that the new links work:
-- Test Script:
https://gist.github.com/dviererbe/0255733d25a27c9a3ddc0bfc9535c243
-- New -latest URLs
- -
https://releases.ubuntu.com/jammy/ubuntu-22.04-latest-live-server-amd64.iso
- - https://releases.ubuntu.com/jammy/ubuntu-22.04-latest-desktop-amd64.iso
+ # see
https://git.launchpad.net/casper/tree/scripts/casper?id=eb5ef85cb33fba28f9ae6e8da6194aaa521d5a49#n267
+ $ wget "${server_url}" -O /dev/null
+
+ # You should observe an ERROR 404: Not Found.
+
+ * Test that the new links work:
+ - Test Script:
https://gist.github.com/dviererbe/0255733d25a27c9a3ddc0bfc9535c243
+ - New -latest URLs
-
https://releases.ubuntu.com/jammy/ubuntu-22.04-latest-live-server-amd64.iso
- https://releases.ubuntu.com/jammy/ubuntu-22.04-latest-desktop-amd64.iso
-
http://cdimage.ubuntu.com/releases/jammy/release/ubuntu-22.04-latest-live-server-arm64.iso
- -
http://cdimage.ubuntu.com/releases/jammy/release/ubuntu-22.04-latest-desktop-arm64.iso
-
http://cdimage.ubuntu.com/releases/jammy/release/ubuntu-22.04-latest-live-server-ppc64el.iso
- -
http://cdimage.ubuntu.com/releases/jammy/release/ubuntu-22.04-latest-desktop-ppc64el.iso
- -
http://cdimage.ubuntu.com/releases/jammy/release/ubuntu-22.04-latest-live-server-riscv64.iso
- -
http://cdimage.ubuntu.com/releases/jammy/release/ubuntu-22.04-latest-desktop-riscv64.iso
-
http://cdimage.ubuntu.com/releases/jammy/release/ubuntu-22.04-latest-live-server-s390x.iso
- -
http://cdimage.ubuntu.com/releases/jammy/release/ubuntu-22.04-latest-desktop-s390x.iso
- * Łukasz Zemczak (sil2100) tested that casper can handle
-HTTP 301 redirects. (See
https://code.launchpad.net/~dviererbe/casper/+git/casper/+merge/446497/comments/1193559)
-
+ * Łukasz Zemczak (sil2100) tested that casper can handle
+ HTTP 301 redirects. (See
[Kernel-packages] [Bug 1990621] Re: PXE Boot contains wrong suggested link to ISO for live file system
** Description changed:
+ [ Impact ]
+
+ * What are the effects of the bug on users?
+casper's intercative netmount fails to download the latest
+Ubuntu LTS ISOs after the release of the first point release
+(e.g. 22.04.1)
+
+ * What is the justification for backporting the fix to the
+There are at least 2 bug reports about this problem
+(LP: #1990621, #1948884) and this fix will improve the
+user experience with a low probaility of side effects.
+
+ * How does the upload fix the bug?
+
+- The patch adds a '-latest' to the download URLs (see more
+ details here:
https://git.launchpad.net/casper/diff/scripts/casper?id=5075686ba44c942e58c71d2c99076fe72fe64022).
+- Additionaly Łukasz Zemczak (sil2100) created symlinks that
+ (as the name of the urls imply) always points to the latest
+ Ubuntu ISO for a given version.
+
+ [ Test Plan ]
+
+ * How to reproduce the bug?
+
+- Just run the failling parts of the casper script on a
+ 22.04.1 <= x < 22.10 machine:
+
+ # would normally be set by initramfs-tools
+ $ DPKG_ARCH=amd64
+
+ # sets UBUNTU_CODENAME=jammy and VERSION_ID="22.04"
+ $ source /etc/os-release
+
+ # see
https://git.launchpad.net/casper/tree/scripts/casper?id=eb5ef85cb33fba28f9ae6e8da6194aaa521d5a49#n388
+ $
server_url=https://releases.ubuntu.com/$UBUNTU_CODENAME/ubuntu-$VERSION_ID-live-server-$DPKG_ARCH.iso
+
+ # see
https://git.launchpad.net/casper/tree/scripts/casper?id=eb5ef85cb33fba28f9ae6e8da6194aaa521d5a49#n267
+ $ wget "${server_url}" -O /dev/null
+
+ # You should observe an ERROR 404: Not Found.
+
+ * Test that the new links work:
+- Test Script:
https://gist.github.com/dviererbe/0255733d25a27c9a3ddc0bfc9535c243
+- New -latest URLs
+ -
https://releases.ubuntu.com/jammy/ubuntu-22.04-latest-live-server-amd64.iso
+ - https://releases.ubuntu.com/jammy/ubuntu-22.04-latest-desktop-amd64.iso
+ -
https://releases.ubuntu.com/jammy/ubuntu-22.04-latest-live-server-amd64.iso
+ - https://releases.ubuntu.com/jammy/ubuntu-22.04-latest-desktop-amd64.iso
+ -
http://cdimage.ubuntu.com/releases/jammy/release/ubuntu-22.04-latest-live-server-arm64.iso
+ -
http://cdimage.ubuntu.com/releases/jammy/release/ubuntu-22.04-latest-desktop-arm64.iso
+ -
http://cdimage.ubuntu.com/releases/jammy/release/ubuntu-22.04-latest-live-server-ppc64el.iso
+ -
http://cdimage.ubuntu.com/releases/jammy/release/ubuntu-22.04-latest-desktop-ppc64el.iso
+ -
http://cdimage.ubuntu.com/releases/jammy/release/ubuntu-22.04-latest-live-server-riscv64.iso
+ -
http://cdimage.ubuntu.com/releases/jammy/release/ubuntu-22.04-latest-desktop-riscv64.iso
+ -
http://cdimage.ubuntu.com/releases/jammy/release/ubuntu-22.04-latest-live-server-s390x.iso
+ -
http://cdimage.ubuntu.com/releases/jammy/release/ubuntu-22.04-latest-desktop-s390x.iso
+
+ * Łukasz Zemczak (sil2100) tested that casper can handle
+HTTP 301 redirects. (See
https://code.launchpad.net/~dviererbe/casper/+git/casper/+merge/446497/comments/1193559)
+
+ [ Where problems could occur ]
+
+ * The Ubuntu Release Team could forget or the automation
+could stop working to update the -latest links, but this
+would, in the worst case, result in a not more worse
+situation than the current bug.
+
+ [ Other Info ]
+
+ * Nick Rosbrook (enr0n) pointed out in comment #3 that the
+script allows the user to provide their own url.
+This should only be considered a temporary workaround as
+a user has to be aware of this bug and has to aquire a
+URL by themself. Copy & pasting URLs from the web is
+potentialy error prone and unsafe.
+
+ * As far as I am aware, there was a discussion between
+Łukasz Zemczak (sil2100), Brian Murray (brian-murray) and
+Steve Langasek (~vorlon) about the link namining. Neither
+was particularly happy about the current solution, but no
+better solution was found.
+
+ * Original Bug report:
+
When PXE booting without pulling in squashfs correctly the system tried
to be helpful (:-) and grab an ISO. The 22.04.1 Jammy release contains a
link to the old version which is not present anymore.
---
Unable to find a medium containing a live file system
Attempt interactive netboot from a URL?
- yes no (default yes):
+ yes no (default yes):
Two methods available for IP configuration:
- * static: for static IP configuration
- * dhcp: for automatic IP configuration
- static dhcp (default 'dhcp'):
- vlan id (optional):
- https://releases.ubuntu.com/jammy/ubuntu-22.04-live-server-amd64.iso
(default)
- https://releases.ubuntu.com/jammy/ubuntu-22.04-desktop-amd64.iso
- url:
- http_proxy (optional):
+ * static: for static IP configuration
+ * dhcp: for automatic IP configuration
+ static dhcp (default 'dhcp'):
+ vlan id (optional):
+
[Kernel-packages] [Bug 1990621] Re: PXE Boot contains wrong suggested link to ISO for live file system
Łukasz Zemczak (sil2100) gave me the greenlight to implement the "-latest" solution. You can find the merge proposal here: https://code.launchpad.net/~dviererbe/casper/+git/casper/+merge/446497 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1990621 Title: PXE Boot contains wrong suggested link to ISO for live file system Status in casper package in Ubuntu: Triaged Status in linux package in Ubuntu: Invalid Status in casper source package in Jammy: Triaged Status in linux source package in Jammy: Invalid Bug description: When PXE booting without pulling in squashfs correctly the system tried to be helpful (:-) and grab an ISO. The 22.04.1 Jammy release contains a link to the old version which is not present anymore. --- Unable to find a medium containing a live file system Attempt interactive netboot from a URL? yes no (default yes): Two methods available for IP configuration: * static: for static IP configuration * dhcp: for automatic IP configuration static dhcp (default 'dhcp'): vlan id (optional): https://releases.ubuntu.com/jammy/ubuntu-22.04-live-server-amd64.iso (default) https://releases.ubuntu.com/jammy/ubuntu-22.04-desktop-amd64.iso url: http_proxy (optional): [ 125.454385] igb :00:14.0 eno1: igb: eno1 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX [ 125.566067] IPv6: ADDRCONF(NETDEV_CHANGE): eno1: link becomes ready Begin: Trying netboot from 10.0.~.1: ... Begin: Trying to download and mount https://releases.ubuntu.com/jammy/ubuntu-22.04-live-server-amd64.iso ... BusyBox v1.30.1 (Ubuntu 1:1.30.1-7ubuntu3) built-in shell (ash) Enter 'help' for a list of built-in commands. (initramfs) Connecting to releases.ubuntu.com (185.125.190.37:443) wget: server returned error: HTTP/1.1 404 Not Found done. Unable to find a medium containing a live file system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1990621/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2019980] Re: autopkgtest ubuntu-regression-suite never passes
Can anyone either fix your autopkgtest ubuntu-regression-suite or mark it as flaky? I am a little bit dumbfounded by the existence of 3 debian folders "debian", "debian.lowlatency" and "debian.master" I don't know how to submit a patch for that -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lowlatency in Ubuntu. https://bugs.launchpad.net/bugs/2019980 Title: autopkgtest ubuntu-regression-suite never passes Status in linux-lowlatency package in Ubuntu: New Bug description: I am currently investigating a proposed migration of git [1]. It is currently blocked due to failing autopkgtests of linux-lowlatency/6.2.0-1004.4 (amd64). I noticed that the failing test ubuntu-regression-suite never passes. It gets either skipped; e.g.: - logs of mantic/amd64 passes [2][3][4] - logs of lunar/amd64 passes [5][6][7] - logs of kinetic/amd64 passes [8][9][10] - logs of jammy/amd64 passes [11][12][13] or fails - logs of mantic/amd64 fails [14][15][16] - logs of lunar/amd64 fails [17][18][19] - logs of kinetic/amd64 fails [20][21][22] - logs of jammy/amd64 fails [23][24][25] See also: All Autopkgtest Cloud Results for linux-lowlatency [26] Links: [1] https://ubuntu-archive-team.ubuntu.com/proposed-migration/update_excuses.html#git [2] https://autopkgtest.ubuntu.com/results/autopkgtest-mantic/mantic/amd64/l/linux-lowlatency/20230508_085948_bb5d7@/log.gz [3] https://autopkgtest.ubuntu.com/results/autopkgtest-mantic/mantic/amd64/l/linux-lowlatency/20230504_072015_4d70b@/log.gz [4] https://autopkgtest.ubuntu.com/results/autopkgtest-mantic/mantic/amd64/l/linux-lowlatency/20230412_113922_b6850@/log.gz [5] https://autopkgtest.ubuntu.com/results/autopkgtest-lunar/lunar/amd64/l/linux-lowlatency/20221212_014258_c2330@/log.gz [6] https://autopkgtest.ubuntu.com/results/autopkgtest-lunar/lunar/amd64/l/linux-lowlatency/20221211_060626_8a5f8@/log.gz [7] https://autopkgtest.ubuntu.com/results/autopkgtest-lunar/lunar/amd64/l/linux-lowlatency/20221209_034534_cbdb7@/log.gz [8] https://autopkgtest.ubuntu.com/results/autopkgtest-kinetic/kinetic/amd64/l/linux-lowlatency/20230328_224621_6a63d@/log.gz [9] https://autopkgtest.ubuntu.com/results/autopkgtest-kinetic/kinetic/amd64/l/linux-lowlatency/20230322_062422_5e68c@/log.gz [10] https://autopkgtest.ubuntu.com/results/autopkgtest-kinetic/kinetic/amd64/l/linux-lowlatency/20221014_063741_d4340@/log.gz [11] https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/amd64/l/linux-lowlatency/20221025_162403_5c773@/log.gz [12] https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/amd64/l/linux-lowlatency/20221117_192249_c8d15@/log.gz [13] https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/amd64/l/linux-lowlatency/20230326_035039_62e35@/log.gz [14] https://autopkgtest.ubuntu.com/results/autopkgtest-mantic/mantic/amd64/l/linux-lowlatency/20230508_101439_9ea48@/log.gz [15] https://autopkgtest.ubuntu.com/results/autopkgtest-mantic/mantic/amd64/l/linux-lowlatency/20230506_105459_9afd8@/log.gz [16] https://autopkgtest.ubuntu.com/results/autopkgtest-mantic/mantic/amd64/l/linux-lowlatency/20230504_122652_0c3cc@/log.gz [17] https://autopkgtest.ubuntu.com/results/autopkgtest-lunar/lunar/amd64/l/linux-lowlatency/20230504_104011_dee5a@/log.gz [18] https://autopkgtest.ubuntu.com/results/autopkgtest-lunar/lunar/amd64/l/linux-lowlatency/20230413_182458_9a7ea@/log.gz [19] https://autopkgtest.ubuntu.com/results/autopkgtest-lunar/lunar/amd64/l/linux-lowlatency/20230426_183943_c55ae@/log.gz [20] https://autopkgtest.ubuntu.com/results/autopkgtest-kinetic/kinetic/amd64/l/linux-lowlatency/20230428_113535_12ddc@/log.gz [21] https://autopkgtest.ubuntu.com/results/autopkgtest-kinetic/kinetic/amd64/l/linux-lowlatency/20221208_221446_fa0db@/log.gz [22] https://autopkgtest.ubuntu.com/results/autopkgtest-kinetic/kinetic/amd64/l/linux-lowlatency/20230321_104259_c1666@/log.gz [23] https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/amd64/l/linux-lowlatency/20230426_190828_2ca69@/log.gz [24] https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/amd64/l/linux-lowlatency/20230322_113837_b4cf8@/log.gz [25] https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/amd64/l/linux-lowlatency/20230216_195232_153c1@/log.gz [26] https://autopkgtest.ubuntu.com/packages/linux-lowlatency To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-lowlatency/+bug/2019980/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2019980] Re: autopkgtest ubuntu-regression-suite never passes
** Tags added: update-excuse -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lowlatency in Ubuntu. https://bugs.launchpad.net/bugs/2019980 Title: autopkgtest ubuntu-regression-suite never passes Status in linux-lowlatency package in Ubuntu: New Bug description: I am currently investigating a proposed migration of git [1]. It is currently blocked due to failing autopkgtests of linux-lowlatency/6.2.0-1004.4 (amd64). I noticed that the failing test ubuntu-regression-suite never passes. It gets either skipped; e.g.: - logs of mantic/amd64 passes [2][3][4] - logs of lunar/amd64 passes [5][6][7] - logs of kinetic/amd64 passes [8][9][10] - logs of jammy/amd64 passes [11][12][13] or fails - logs of mantic/amd64 fails [14][15][16] - logs of lunar/amd64 fails [17][18][19] - logs of kinetic/amd64 fails [20][21][22] - logs of jammy/amd64 fails [23][24][25] See also: All Autopkgtest Cloud Results for linux-lowlatency [26] Links: [1] https://ubuntu-archive-team.ubuntu.com/proposed-migration/update_excuses.html#git [2] https://autopkgtest.ubuntu.com/results/autopkgtest-mantic/mantic/amd64/l/linux-lowlatency/20230508_085948_bb5d7@/log.gz [3] https://autopkgtest.ubuntu.com/results/autopkgtest-mantic/mantic/amd64/l/linux-lowlatency/20230504_072015_4d70b@/log.gz [4] https://autopkgtest.ubuntu.com/results/autopkgtest-mantic/mantic/amd64/l/linux-lowlatency/20230412_113922_b6850@/log.gz [5] https://autopkgtest.ubuntu.com/results/autopkgtest-lunar/lunar/amd64/l/linux-lowlatency/20221212_014258_c2330@/log.gz [6] https://autopkgtest.ubuntu.com/results/autopkgtest-lunar/lunar/amd64/l/linux-lowlatency/20221211_060626_8a5f8@/log.gz [7] https://autopkgtest.ubuntu.com/results/autopkgtest-lunar/lunar/amd64/l/linux-lowlatency/20221209_034534_cbdb7@/log.gz [8] https://autopkgtest.ubuntu.com/results/autopkgtest-kinetic/kinetic/amd64/l/linux-lowlatency/20230328_224621_6a63d@/log.gz [9] https://autopkgtest.ubuntu.com/results/autopkgtest-kinetic/kinetic/amd64/l/linux-lowlatency/20230322_062422_5e68c@/log.gz [10] https://autopkgtest.ubuntu.com/results/autopkgtest-kinetic/kinetic/amd64/l/linux-lowlatency/20221014_063741_d4340@/log.gz [11] https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/amd64/l/linux-lowlatency/20221025_162403_5c773@/log.gz [12] https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/amd64/l/linux-lowlatency/20221117_192249_c8d15@/log.gz [13] https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/amd64/l/linux-lowlatency/20230326_035039_62e35@/log.gz [14] https://autopkgtest.ubuntu.com/results/autopkgtest-mantic/mantic/amd64/l/linux-lowlatency/20230508_101439_9ea48@/log.gz [15] https://autopkgtest.ubuntu.com/results/autopkgtest-mantic/mantic/amd64/l/linux-lowlatency/20230506_105459_9afd8@/log.gz [16] https://autopkgtest.ubuntu.com/results/autopkgtest-mantic/mantic/amd64/l/linux-lowlatency/20230504_122652_0c3cc@/log.gz [17] https://autopkgtest.ubuntu.com/results/autopkgtest-lunar/lunar/amd64/l/linux-lowlatency/20230504_104011_dee5a@/log.gz [18] https://autopkgtest.ubuntu.com/results/autopkgtest-lunar/lunar/amd64/l/linux-lowlatency/20230413_182458_9a7ea@/log.gz [19] https://autopkgtest.ubuntu.com/results/autopkgtest-lunar/lunar/amd64/l/linux-lowlatency/20230426_183943_c55ae@/log.gz [20] https://autopkgtest.ubuntu.com/results/autopkgtest-kinetic/kinetic/amd64/l/linux-lowlatency/20230428_113535_12ddc@/log.gz [21] https://autopkgtest.ubuntu.com/results/autopkgtest-kinetic/kinetic/amd64/l/linux-lowlatency/20221208_221446_fa0db@/log.gz [22] https://autopkgtest.ubuntu.com/results/autopkgtest-kinetic/kinetic/amd64/l/linux-lowlatency/20230321_104259_c1666@/log.gz [23] https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/amd64/l/linux-lowlatency/20230426_190828_2ca69@/log.gz [24] https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/amd64/l/linux-lowlatency/20230322_113837_b4cf8@/log.gz [25] https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/amd64/l/linux-lowlatency/20230216_195232_153c1@/log.gz [26] https://autopkgtest.ubuntu.com/packages/linux-lowlatency To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-lowlatency/+bug/2019980/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 2019980] [NEW] autopkgtest ubuntu-regression-suite never passes
Public bug reported: I am currently investigating a proposed migration of git [1]. It is currently blocked due to failing autopkgtests of linux-lowlatency/6.2.0-1004.4 (amd64). I noticed that the failing test ubuntu-regression-suite never passes. It gets either skipped; e.g.: - logs of mantic/amd64 passes [2][3][4] - logs of lunar/amd64 passes [5][6][7] - logs of kinetic/amd64 passes [8][9][10] - logs of jammy/amd64 passes [11][12][13] or fails - logs of mantic/amd64 fails [14][15][16] - logs of lunar/amd64 fails [17][18][19] - logs of kinetic/amd64 fails [20][21][22] - logs of jammy/amd64 fails [23][24][25] See also: All Autopkgtest Cloud Results for linux-lowlatency [26] Links: [1] https://ubuntu-archive-team.ubuntu.com/proposed-migration/update_excuses.html#git [2] https://autopkgtest.ubuntu.com/results/autopkgtest-mantic/mantic/amd64/l/linux-lowlatency/20230508_085948_bb5d7@/log.gz [3] https://autopkgtest.ubuntu.com/results/autopkgtest-mantic/mantic/amd64/l/linux-lowlatency/20230504_072015_4d70b@/log.gz [4] https://autopkgtest.ubuntu.com/results/autopkgtest-mantic/mantic/amd64/l/linux-lowlatency/20230412_113922_b6850@/log.gz [5] https://autopkgtest.ubuntu.com/results/autopkgtest-lunar/lunar/amd64/l/linux-lowlatency/20221212_014258_c2330@/log.gz [6] https://autopkgtest.ubuntu.com/results/autopkgtest-lunar/lunar/amd64/l/linux-lowlatency/20221211_060626_8a5f8@/log.gz [7] https://autopkgtest.ubuntu.com/results/autopkgtest-lunar/lunar/amd64/l/linux-lowlatency/20221209_034534_cbdb7@/log.gz [8] https://autopkgtest.ubuntu.com/results/autopkgtest-kinetic/kinetic/amd64/l/linux-lowlatency/20230328_224621_6a63d@/log.gz [9] https://autopkgtest.ubuntu.com/results/autopkgtest-kinetic/kinetic/amd64/l/linux-lowlatency/20230322_062422_5e68c@/log.gz [10] https://autopkgtest.ubuntu.com/results/autopkgtest-kinetic/kinetic/amd64/l/linux-lowlatency/20221014_063741_d4340@/log.gz [11] https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/amd64/l/linux-lowlatency/20221025_162403_5c773@/log.gz [12] https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/amd64/l/linux-lowlatency/20221117_192249_c8d15@/log.gz [13] https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/amd64/l/linux-lowlatency/20230326_035039_62e35@/log.gz [14] https://autopkgtest.ubuntu.com/results/autopkgtest-mantic/mantic/amd64/l/linux-lowlatency/20230508_101439_9ea48@/log.gz [15] https://autopkgtest.ubuntu.com/results/autopkgtest-mantic/mantic/amd64/l/linux-lowlatency/20230506_105459_9afd8@/log.gz [16] https://autopkgtest.ubuntu.com/results/autopkgtest-mantic/mantic/amd64/l/linux-lowlatency/20230504_122652_0c3cc@/log.gz [17] https://autopkgtest.ubuntu.com/results/autopkgtest-lunar/lunar/amd64/l/linux-lowlatency/20230504_104011_dee5a@/log.gz [18] https://autopkgtest.ubuntu.com/results/autopkgtest-lunar/lunar/amd64/l/linux-lowlatency/20230413_182458_9a7ea@/log.gz [19] https://autopkgtest.ubuntu.com/results/autopkgtest-lunar/lunar/amd64/l/linux-lowlatency/20230426_183943_c55ae@/log.gz [20] https://autopkgtest.ubuntu.com/results/autopkgtest-kinetic/kinetic/amd64/l/linux-lowlatency/20230428_113535_12ddc@/log.gz [21] https://autopkgtest.ubuntu.com/results/autopkgtest-kinetic/kinetic/amd64/l/linux-lowlatency/20221208_221446_fa0db@/log.gz [22] https://autopkgtest.ubuntu.com/results/autopkgtest-kinetic/kinetic/amd64/l/linux-lowlatency/20230321_104259_c1666@/log.gz [23] https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/amd64/l/linux-lowlatency/20230426_190828_2ca69@/log.gz [24] https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/amd64/l/linux-lowlatency/20230322_113837_b4cf8@/log.gz [25] https://autopkgtest.ubuntu.com/results/autopkgtest-jammy/jammy/amd64/l/linux-lowlatency/20230216_195232_153c1@/log.gz [26] https://autopkgtest.ubuntu.com/packages/linux-lowlatency ** Affects: linux-lowlatency (Ubuntu) Importance: Undecided Status: New ** Tags: update-excuse -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-lowlatency in Ubuntu. https://bugs.launchpad.net/bugs/2019980 Title: autopkgtest ubuntu-regression-suite never passes Status in linux-lowlatency package in Ubuntu: New Bug description: I am currently investigating a proposed migration of git [1]. It is currently blocked due to failing autopkgtests of linux-lowlatency/6.2.0-1004.4 (amd64). I noticed that the failing test ubuntu-regression-suite never passes. It gets either skipped; e.g.: - logs of mantic/amd64 passes [2][3][4] - logs of lunar/amd64 passes [5][6][7] - logs of kinetic/amd64 passes [8][9][10] - logs of jammy/amd64 passes [11][12][13] or fails - logs of mantic/amd64 fails [14][15][16] - logs of lunar/amd64 fails [17][18][19] - logs of kinetic/amd64 fails [20][21][22] - logs of jammy/amd64 fails [23][24][25] See also: All Autopkgtest Cloud Results for linux-lowlatency [26] Links: [1]
[Kernel-packages] [Bug 2018297] Re: ThinkPad Yoga 460 Auto-Rotation stoped working after suspension
I can not replicate the state when the "Orientation" setting in the "Display Settings" Menu shows no dropdown menu when clicked. I will set this bug also to "Incomplete" for "gnome-shell (Ubuntu)" ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/2018297 Title: ThinkPad Yoga 460 Auto-Rotation stoped working after suspension Status in gnome-shell package in Ubuntu: Incomplete Status in iio-sensor-proxy package in Ubuntu: Invalid Status in linux package in Ubuntu: Incomplete Bug description: The auto-rotation feature of my Laptop stoped working. - screen orientation was in landscape mode - closed the lid of my laptop => laptop entered suspension mode - opened the lid => laptop was waking up - screen orientation was in portait mode I could not change the screen orientation by rotating the laptop physically nor change the orientation manually (the "Orientation" setting in the "Display Settings" Menu showed no dropdown menu). After a quick reboot everything worked fine. This are the specs of my Device: OS: Ubuntu 23.04 x86_64 Host: 20EM000VGE ThinkPad Yoga 460 Kernel: 6.2.0-20-generic Resolution: 1920x1080 DE: GNOME 44.0 WM: Mutter WM Theme: Adwaita Theme: Yaru [GTK2/3] Icons: Yaru [GTK2/3] CPU: Intel i7-6500U (4) @ 3.100GHz GPU: Intel Skylake GT2 [HD Graphics 520] Memory: 7682MiB To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2018297/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1990621] Re: PXE Boot contains wrong suggested link to ISO for live file system
I talked today to Łukasz Zemczak (sil2100) about the redirection. He made some pretty good arguments that the name of the URL should match a user's expectations. E.g. a User could assume the URL "https://releases.ubuntu.com/jammy/ubuntu-22.04-live-server-amd64.iso; will provide the initial version of 22.04 and not the latest point release. I suggested a URL style like this "https://releases.ubuntu.com/jammy/ubuntu-22.04-latest-live-server- amd64.iso" (notice the "-latest" after the version id). -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1990621 Title: PXE Boot contains wrong suggested link to ISO for live file system Status in casper package in Ubuntu: Triaged Status in linux package in Ubuntu: Invalid Status in casper source package in Jammy: Triaged Status in linux source package in Jammy: Invalid Bug description: When PXE booting without pulling in squashfs correctly the system tried to be helpful (:-) and grab an ISO. The 22.04.1 Jammy release contains a link to the old version which is not present anymore. --- Unable to find a medium containing a live file system Attempt interactive netboot from a URL? yes no (default yes): Two methods available for IP configuration: * static: for static IP configuration * dhcp: for automatic IP configuration static dhcp (default 'dhcp'): vlan id (optional): https://releases.ubuntu.com/jammy/ubuntu-22.04-live-server-amd64.iso (default) https://releases.ubuntu.com/jammy/ubuntu-22.04-desktop-amd64.iso url: http_proxy (optional): [ 125.454385] igb :00:14.0 eno1: igb: eno1 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX [ 125.566067] IPv6: ADDRCONF(NETDEV_CHANGE): eno1: link becomes ready Begin: Trying netboot from 10.0.~.1: ... Begin: Trying to download and mount https://releases.ubuntu.com/jammy/ubuntu-22.04-live-server-amd64.iso ... BusyBox v1.30.1 (Ubuntu 1:1.30.1-7ubuntu3) built-in shell (ash) Enter 'help' for a list of built-in commands. (initramfs) Connecting to releases.ubuntu.com (185.125.190.37:443) wget: server returned error: HTTP/1.1 404 Not Found done. Unable to find a medium containing a live file system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1990621/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1990621] Re: PXE Boot contains wrong suggested link to ISO for live file system
Here is a possible implementation for parsing the point release number from "$VERSION. ** Patch added: "LP#1990621-bugfix.debdiff" https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1990621/+attachment/5648668/+files/LP%231990621-bugfix.debdiff -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1990621 Title: PXE Boot contains wrong suggested link to ISO for live file system Status in casper package in Ubuntu: Triaged Status in linux package in Ubuntu: Invalid Status in casper source package in Jammy: Triaged Status in linux source package in Jammy: Invalid Bug description: When PXE booting without pulling in squashfs correctly the system tried to be helpful (:-) and grab an ISO. The 22.04.1 Jammy release contains a link to the old version which is not present anymore. --- Unable to find a medium containing a live file system Attempt interactive netboot from a URL? yes no (default yes): Two methods available for IP configuration: * static: for static IP configuration * dhcp: for automatic IP configuration static dhcp (default 'dhcp'): vlan id (optional): https://releases.ubuntu.com/jammy/ubuntu-22.04-live-server-amd64.iso (default) https://releases.ubuntu.com/jammy/ubuntu-22.04-desktop-amd64.iso url: http_proxy (optional): [ 125.454385] igb :00:14.0 eno1: igb: eno1 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX [ 125.566067] IPv6: ADDRCONF(NETDEV_CHANGE): eno1: link becomes ready Begin: Trying netboot from 10.0.~.1: ... Begin: Trying to download and mount https://releases.ubuntu.com/jammy/ubuntu-22.04-live-server-amd64.iso ... BusyBox v1.30.1 (Ubuntu 1:1.30.1-7ubuntu3) built-in shell (ash) Enter 'help' for a list of built-in commands. (initramfs) Connecting to releases.ubuntu.com (185.125.190.37:443) wget: server returned error: HTTP/1.1 404 Not Found done. Unable to find a medium containing a live file system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1990621/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1990621] Re: PXE Boot contains wrong suggested link to ISO for live file system
I did some research today. I think this bug affects all LTS releases. As Nick Rosbrook (enr0n) suggested we can use $VERSION to parse the version id with the point release number like this $(echo "$VERSION"| grep -o -s -E '^[0-9\.]+') , but this would still not fix the bug for all LTS users who haven't the most up to date /etc/os-release file. For example: When 22.04.02 gets released; a user that hasn't updated yet still has an /etc/os-release file with the value VERSION="22.04.1 LTS (Jammy Jellyfish)" This would still result in a broken link. Alternative solutions would be: 1. using a web-crawler that looks for the latest release url (overcomplicated) 2. setting up a redirection from the "broken" url to the correct one Alternative 2 would result in an instant-fix without needing the user to update and is simple. I have to find out who I would need to ask for that. ** Changed in: casper (Ubuntu Jammy) Assignee: (unassigned) => Dominik Viererbe (dviererbe) ** Changed in: casper (Ubuntu) Assignee: (unassigned) => Dominik Viererbe (dviererbe) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1990621 Title: PXE Boot contains wrong suggested link to ISO for live file system Status in casper package in Ubuntu: Triaged Status in linux package in Ubuntu: Invalid Status in casper source package in Jammy: Triaged Status in linux source package in Jammy: Invalid Bug description: When PXE booting without pulling in squashfs correctly the system tried to be helpful (:-) and grab an ISO. The 22.04.1 Jammy release contains a link to the old version which is not present anymore. --- Unable to find a medium containing a live file system Attempt interactive netboot from a URL? yes no (default yes): Two methods available for IP configuration: * static: for static IP configuration * dhcp: for automatic IP configuration static dhcp (default 'dhcp'): vlan id (optional): https://releases.ubuntu.com/jammy/ubuntu-22.04-live-server-amd64.iso (default) https://releases.ubuntu.com/jammy/ubuntu-22.04-desktop-amd64.iso url: http_proxy (optional): [ 125.454385] igb :00:14.0 eno1: igb: eno1 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX/TX [ 125.566067] IPv6: ADDRCONF(NETDEV_CHANGE): eno1: link becomes ready Begin: Trying netboot from 10.0.~.1: ... Begin: Trying to download and mount https://releases.ubuntu.com/jammy/ubuntu-22.04-live-server-amd64.iso ... BusyBox v1.30.1 (Ubuntu 1:1.30.1-7ubuntu3) built-in shell (ash) Enter 'help' for a list of built-in commands. (initramfs) Connecting to releases.ubuntu.com (185.125.190.37:443) wget: server returned error: HTTP/1.1 404 Not Found done. Unable to find a medium containing a live file system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/casper/+bug/1990621/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
