[Touch-packages] [Bug 1660762] Re: [Regression] Interface configuration not restored after driver unbind/bind (generic)
** Changed in: ifupdown (Ubuntu) Importance: Undecided => High ** Changed in: ifupdown (Ubuntu) Status: New => Triaged ** Changed in: ifupdown (Ubuntu) Assignee: Taco Screen team (taco-screen-team) => Canonical Kernel Team (canonical-kernel-team) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ifupdown in Ubuntu. https://bugs.launchpad.net/bugs/1660762 Title: [Regression] Interface configuration not restored after driver unbind/bind (generic) Status in ifupdown package in Ubuntu: Triaged Bug description: ---Problem Description--- Interface configuration not restored after driver unbind/bind root@ltciofvtr-s824-lp8:~# ifconfig enP28p96s0f0 enP28p96s0f0: flags=4163 mtu 1500 inet 10.10.10.11 netmask 255.255.255.0 broadcast 10.10.10.255 inet6 fe80::290:faff:fe7a:5840 prefixlen 64 scopeid 0x20 ether 00:90:fa:7a:58:40 txqueuelen 1000 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 13 bytes 1046 (1.0 KB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 root@ltciofvtr-s824-lp8:~# cat /etc/network/interfaces # This file describes the network interfaces available on your system # and how to activate them. For more information, see interfaces(5). source /etc/network/interfaces.d/* # The loopback network interface auto lo iface lo inet loopback # The primary network interface auto ibmveth2 iface ibmveth2 inet static address 9.47.68.120 netmask 255.255.240.0 network 9.47.64.0 broadcast 9.47.79.255 gateway 9.47.79.254 # dns-* options are implemented by the resolvconf package, if installed dns-nameservers 9.12.18.2 dns-search pok.stglabs.ibm.com auto enP28p96s0f0 iface enP28p96s0f0 inet static address 10.10.10.11 netmask 255.255.255.0 root@ltciofvtr-s824-lp8:~# ethtool -i enP28p96s0f0 driver: be2net version: 11.1.0.0 firmware-version: 10.2.252.1913 expansion-rom-version: bus-info: 001c:60:00.0 supports-statistics: yes supports-test: yes supports-eeprom-access: yes supports-register-dump: no supports-priv-flags: yes root@ltciofvtr-s824-lp8:~# echo -n 001c:60:00.0 > /sys/bus/pci/drivers/be2net/unbind root@ltciofvtr-s824-lp8:~# ls /sys/bus/pci/drivers/be2net 001c:60:00.1 001c:60:00.2 001c:60:00.3 bind module new_id remove_id uevent unbind root@ltciofvtr-s824-lp8:~# echo -n 001c:60:00.0 > /sys/bus/pci/drivers/be2net/bind root@ltciofvtr-s824-lp8:~# ls /sys/bus/pci/drivers/be2net 001c:60:00.0 001c:60:00.1 001c:60:00.2 001c:60:00.3 bind module new_id remove_id uevent unbind root@ltciofvtr-s824-lp8:~# ifconfig enP28p96s0f0 enP28p96s0f0: flags=4098 mtu 1500 ether 00:90:fa:7a:58:40 txqueuelen 1000 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 root@ltciofvtr-s824-lp8:~# ifup enP28p96s0f0 ifup: interface enP28p96s0f0 already configured root@ltciofvtr-s824-lp8:~# ifdown enP28p96s0f0 RTNETLINK answers: Cannot assign requested address root@ltciofvtr-s824-lp8:~# ifup enP28p96s0f0 root@ltciofvtr-s824-lp8:~# ifconfig enP28p96s0f0 enP28p96s0f0: flags=4163 mtu 1500 inet 10.10.10.11 netmask 255.255.255.0 broadcast 10.10.10.255 inet6 fe80::290:faff:fe7a:5840 prefixlen 64 scopeid 0x20 ether 00:90:fa:7a:58:40 txqueuelen 1000 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 16 bytes 1344 (1.3 KB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 ---uname output--- Linux ltciofvtr-s824-lp8 4.9.0-12-generic #13-Ubuntu SMP Tue Jan 10 12:52:39 UTC 2017 ppc64le ppc64le ppc64le GNU/Linux Machine Type = IBM,8286-42A LPAR ---Steps to Reproduce--- # echo -n 001c:60:00.0 > /sys/bus/pci/drivers/be2net/unbind # echo -n 001c:60:00.0 > /sys/bus/pci/drivers/be2net/bind == Comment - Vaishnavi Bhat Hi, To bind a device to a driver, the device must first not be controlled by any other driver. Can you check for 'driver' in the below before you bind ? $ tree /sys//bus/pci/devices/001c:60:00.0 Thank you. == Comment - Murilo Fossa Vicentini Just adding some information, this is not a driver specific issue, this was also seen with tg3 and i40e adapters . This behavior is a regression when compared to Ubuntu 16.04 where the interfaces where properly reconfigured upon bind with the information set in /etc/network/interfaces To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1660762/+subscriptions -- Mailing list:
[Touch-packages] [Bug 1639920] Re: NVMe detection failed during bootup
** Package changed: apport (Ubuntu) => linux (Ubuntu) ** Changed in: linux (Ubuntu) Importance: Undecided => High ** Changed in: linux (Ubuntu) Status: New => Triaged -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1639920 Title: NVMe detection failed during bootup Status in linux package in Ubuntu: Triaged Bug description: I've been running an on-off test on a couple of Power8 systems and have been getting a failure of detection on the NVMe drives on Ubuntu 16.04.1 only. I've ran the same test on RHEL 7.2 and have not encountered this proble. Once the problem occurs the OS will stop to boot up and a message appears: Welcome to emergency mode! After logging in, type "journalctl -xb" to view system logs, "systemctl reboot" to reboot, "systemctl default" or ^D to try again to boot into default mode. Give root password for maintenance (or press Control-D to continue): ProblemType: Crash DistroRelease: Ubuntu 16.04 Package: apport 2.20.1-0ubuntu2.1 ProcVersionSignature: Ubuntu 4.4.0-45.66-generic 4.4.21 Uname: Linux 4.4.0-45-generic ppc64le ApportVersion: 2.20.1-0ubuntu2.1 Architecture: ppc64el CrashReports: 640:0:116:12295:2016-11-07 11:11:27.995107650 -0800:2016-11-07 11:31:31.733627559 -0800:/var/crash/_usr_bin_apport-bug.0.crash 644:0:116:0:2016-11-07 11:11:28.931104586 -0800:2016-11-07 11:11:28.931104586 -0800:/var/crash/_usr_bin_apport-cli.0.None.hanging Date: Mon Nov 7 11:11:28 2016 ExecutablePath: /usr/bin/apport-bug InstallationDate: Installed on 2016-11-05 (2 days ago) InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release ppc64el (20160719) InterpreterPath: /usr/bin/python3.5 PackageArchitecture: all ProcCmdline: /usr/bin/python3 /usr/bin/apport-cli --hanging ProcEnviron: TERM=linux PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcLoadAvg: 0.30 0.41 0.19 1/1132 2428 ProcLocks: ProcSwaps: Filename TypeSizeUsedPriority /dev/sda3 partition157914048 0 -1 ProcVersion: Linux version 4.4.0-45-generic (buildd@bos01-ppc64el-030) (gcc version 5.4.0 20160609 (Ubuntu/IBM 5.4.0-6ubuntu1~16.04.2) ) #66-Ubuntu SMP Wed Oct 19 14:13:11 UTC 2016 PythonArgs: ['/usr/bin/ubuntu-bug', '--hanging'] SourcePackage: apport Title: apport-bug crashed with TypeError in run_hang(): int() argument must be a string, a bytes-like object or a number, not 'NoneType' UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: cpu_cores: Number of cores present = 20 cpu_coreson: Number of cores online = 20 cpu_smt: SMT=8 mtime.conffile..etc.apport.crashdb.conf: 2016-11-07T10:38:18.528739 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1639920/+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 1464442] Re: installing or upgrading libc6 in Trusty removes all content from /tmp directory
** Also affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to eglibc in Ubuntu. https://bugs.launchpad.net/bugs/1464442 Title: installing or upgrading libc6 in Trusty removes all content from /tmp directory Status in eglibc package in Ubuntu: Invalid Status in linux package in Ubuntu: New Bug description: We are seeing an issue with installation of dkms package during a curtin installation which ends up with /tmp directory being wiped clean. This is very bad for curtin as it saves critical installation files in /tmp. It turns out that it's the of upgrading libc6, which is triggered as a result of installing dependencies, that removes content of /tmp. For example, installation of gcc results in the same result since it ends up with libc6 being upgraded. The only way that this won't be recreated is if the latest libc6 is already installed. This problem does not exist in precise. It can also be recreated by installing the .deb file for any version in trusty including 2.17. ubuntu@host:~$ ls /tmp tmpHHbRkP ubuntu@sirrush:~$ sudo apt-get install libc6 sudo: unable to resolve host sirrush Reading package lists... Done Building dependency tree Reading state information... Done The following extra packages will be installed: libc-dev-bin libc6-dev Suggested packages: glibc-doc Recommended packages: manpages-dev The following packages will be upgraded: libc-dev-bin libc6 libc6-dev 3 upgraded, 0 newly installed, 0 to remove and 148 not upgraded. Need to get 6,714 kB of archives. After this operation, 6,144 B disk space will be freed. Do you want to continue? [Y/n] y Get:1 http://archive.ubuntu.com/ubuntu/ trusty-updates/main libc6-dev amd64 2.19-0ubuntu6.6 [1,910 kB] Get:2 http://archive.ubuntu.com/ubuntu/ trusty-updates/main libc-dev-bin amd64 2.19-0ubuntu6.6 [68.9 kB] Get:3 http://archive.ubuntu.com/ubuntu/ trusty-updates/main libc6 amd64 2.19-0ubuntu6.6 [4,735 kB] Fetched 6,714 kB in 0s (18.5 MB/s) Preconfiguring packages ... (Reading database ... 57798 files and directories currently installed.) Preparing to unpack .../libc6-dev_2.19-0ubuntu6.6_amd64.deb ... Unpacking libc6-dev:amd64 (2.19-0ubuntu6.6) over (2.19-0ubuntu6.3) ... Preparing to unpack .../libc-dev-bin_2.19-0ubuntu6.6_amd64.deb ... Unpacking libc-dev-bin (2.19-0ubuntu6.6) over (2.19-0ubuntu6.3) ... Preparing to unpack .../libc6_2.19-0ubuntu6.6_amd64.deb ... Unpacking libc6:amd64 (2.19-0ubuntu6.6) over (2.19-0ubuntu6.3) ... Processing triggers for man-db (2.6.7.1-1) ... Setting up libc6:amd64 (2.19-0ubuntu6.6) ... Setting up libc-dev-bin (2.19-0ubuntu6.6) ... Setting up libc6-dev:amd64 (2.19-0ubuntu6.6) ... Processing triggers for libc-bin (2.19-0ubuntu6.3) ... ubuntu@host:~$ ls /tmp ubuntu@host:~$ This is very recreatable. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/eglibc/+bug/1464442/+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 1463836] Re: 4.0 kernel build failure on ppc64el
Still getting you command line options... -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to binutils in Ubuntu. https://bugs.launchpad.net/bugs/1463836 Title: 4.0 kernel build failure on ppc64el Status in binutils package in Ubuntu: New Bug description: We have uploaded our first 4.0 based Wily kernel to the archive but are unfortunately seeing the following build failure which we believe is related to our wily toolchain: https://launchpadlibrarian.net/208665203/buildlog_ubuntu-wily- ppc64el.linux_4.0.0-1.1_BUILDING.txt.gz /build/buildd/linux-4.0.0/arch/powerpc/kernel/swsusp_asm64.S: Assembler messages: /build/buildd/linux-4.0.0/arch/powerpc/kernel/swsusp_asm64.S:188: Error: missing operand /build/buildd/linux-4.0.0/scripts/Makefile.build:294: recipe for target 'arch/powerpc/kernel/swsusp_asm64.o' failed make[3]: *** [arch/powerpc/kernel/swsusp_asm64.o] Error 1 /build/buildd/linux-4.0.0/Makefile:957: recipe for target 'arch/powerpc/kernel' failed make[2]: *** [arch/powerpc/kernel] Error 2 We do not believe this is due to a kernel change as the code in question has not changed in years. Additionally, we had 4.0 based test builds successfully passing in our PPA (ppa:canonical-kernel- team/ppa). The last successful test build in our PPA was from May 21 (the logs are still there if needed). We were also unable to reproduce by cross-compiling. As added information, our wily kernel git repo can be seen at: https://git.launchpad.net/~ubuntu- kernel/ubuntu/+source/linux/+git/wily Let us know if any additional information is required to debug this. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: binutils 2.25-8ubuntu1 ProcVersionSignature: Ubuntu 4.0.0-1.1-generic 4.0.5 Uname: Linux 4.0.0-1-generic x86_64 ApportVersion: 2.17.3-0ubuntu4 Architecture: amd64 CurrentDesktop: Unity Date: Wed Jun 10 06:16:10 2015 Dependencies: gcc-5-base 5.1.1-9ubuntu2 libc6 2.21-0ubuntu4 libgcc1 1:5.1.1-9ubuntu2 multiarch-support 2.21-0ubuntu4 zlib1g 1:1.2.8.dfsg-2ubuntu1 EcryptfsInUse: Yes InstallationDate: Installed on 2014-03-17 (449 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140317) SourcePackage: binutils UpgradeStatus: Upgraded to wily on 2015-05-28 (12 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1463836/+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 1463836] Re: 4.0 kernel build failure on ppc64el
https://git.launchpad.net/~ubuntu- kernel/ubuntu/+source/linux/+git/wily/tree/arch/powerpc/kernel/swsusp_asm64.S -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to binutils in Ubuntu. https://bugs.launchpad.net/bugs/1463836 Title: 4.0 kernel build failure on ppc64el Status in binutils package in Ubuntu: New Bug description: We have uploaded our first 4.0 based Wily kernel to the archive but are unfortunately seeing the following build failure which we believe is related to our wily toolchain: https://launchpadlibrarian.net/208665203/buildlog_ubuntu-wily- ppc64el.linux_4.0.0-1.1_BUILDING.txt.gz /build/buildd/linux-4.0.0/arch/powerpc/kernel/swsusp_asm64.S: Assembler messages: /build/buildd/linux-4.0.0/arch/powerpc/kernel/swsusp_asm64.S:188: Error: missing operand /build/buildd/linux-4.0.0/scripts/Makefile.build:294: recipe for target 'arch/powerpc/kernel/swsusp_asm64.o' failed make[3]: *** [arch/powerpc/kernel/swsusp_asm64.o] Error 1 /build/buildd/linux-4.0.0/Makefile:957: recipe for target 'arch/powerpc/kernel' failed make[2]: *** [arch/powerpc/kernel] Error 2 We do not believe this is due to a kernel change as the code in question has not changed in years. Additionally, we had 4.0 based test builds successfully passing in our PPA (ppa:canonical-kernel- team/ppa). The last successful test build in our PPA was from May 21 (the logs are still there if needed). We were also unable to reproduce by cross-compiling. As added information, our wily kernel git repo can be seen at: https://git.launchpad.net/~ubuntu- kernel/ubuntu/+source/linux/+git/wily Let us know if any additional information is required to debug this. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: binutils 2.25-8ubuntu1 ProcVersionSignature: Ubuntu 4.0.0-1.1-generic 4.0.5 Uname: Linux 4.0.0-1-generic x86_64 ApportVersion: 2.17.3-0ubuntu4 Architecture: amd64 CurrentDesktop: Unity Date: Wed Jun 10 06:16:10 2015 Dependencies: gcc-5-base 5.1.1-9ubuntu2 libc6 2.21-0ubuntu4 libgcc1 1:5.1.1-9ubuntu2 multiarch-support 2.21-0ubuntu4 zlib1g 1:1.2.8.dfsg-2ubuntu1 EcryptfsInUse: Yes InstallationDate: Installed on 2014-03-17 (449 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140317) SourcePackage: binutils UpgradeStatus: Upgraded to wily on 2015-05-28 (12 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1463836/+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 1463836] [NEW] 4.0 kernel build failure on ppc64el
Public bug reported: We have uploaded our first 4.0 based Wily kernel to the archive but are unfortunately seeing the following build failure which we believe is related to our wily toolchain: https://launchpadlibrarian.net/208665203/buildlog_ubuntu-wily- ppc64el.linux_4.0.0-1.1_BUILDING.txt.gz /build/buildd/linux-4.0.0/arch/powerpc/kernel/swsusp_asm64.S: Assembler messages: /build/buildd/linux-4.0.0/arch/powerpc/kernel/swsusp_asm64.S:188: Error: missing operand /build/buildd/linux-4.0.0/scripts/Makefile.build:294: recipe for target 'arch/powerpc/kernel/swsusp_asm64.o' failed make[3]: *** [arch/powerpc/kernel/swsusp_asm64.o] Error 1 /build/buildd/linux-4.0.0/Makefile:957: recipe for target 'arch/powerpc/kernel' failed make[2]: *** [arch/powerpc/kernel] Error 2 We do not believe this is due to a kernel change as the code in question has not changed in years. Additionally, we had 4.0 based test builds successfully passing in our PPA (ppa:canonical-kernel-team/ppa). The last successful test build in our PPA was from May 21 (the logs are still there if needed). We were also unable to reproduce by cross- compiling. As added information, our wily kernel git repo can be seen at: https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/wily Let us know if any additional information is required to debug this. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: binutils 2.25-8ubuntu1 ProcVersionSignature: Ubuntu 4.0.0-1.1-generic 4.0.5 Uname: Linux 4.0.0-1-generic x86_64 ApportVersion: 2.17.3-0ubuntu4 Architecture: amd64 CurrentDesktop: Unity Date: Wed Jun 10 06:16:10 2015 Dependencies: gcc-5-base 5.1.1-9ubuntu2 libc6 2.21-0ubuntu4 libgcc1 1:5.1.1-9ubuntu2 multiarch-support 2.21-0ubuntu4 zlib1g 1:1.2.8.dfsg-2ubuntu1 EcryptfsInUse: Yes InstallationDate: Installed on 2014-03-17 (449 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140317) SourcePackage: binutils UpgradeStatus: Upgraded to wily on 2015-05-28 (12 days ago) ** Affects: binutils (Ubuntu) Importance: Undecided Assignee: Matthias Klose (doko) Status: New ** Tags: amd64 apport-bug wily -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to binutils in Ubuntu. https://bugs.launchpad.net/bugs/1463836 Title: 4.0 kernel build failure on ppc64el Status in binutils package in Ubuntu: New Bug description: We have uploaded our first 4.0 based Wily kernel to the archive but are unfortunately seeing the following build failure which we believe is related to our wily toolchain: https://launchpadlibrarian.net/208665203/buildlog_ubuntu-wily- ppc64el.linux_4.0.0-1.1_BUILDING.txt.gz /build/buildd/linux-4.0.0/arch/powerpc/kernel/swsusp_asm64.S: Assembler messages: /build/buildd/linux-4.0.0/arch/powerpc/kernel/swsusp_asm64.S:188: Error: missing operand /build/buildd/linux-4.0.0/scripts/Makefile.build:294: recipe for target 'arch/powerpc/kernel/swsusp_asm64.o' failed make[3]: *** [arch/powerpc/kernel/swsusp_asm64.o] Error 1 /build/buildd/linux-4.0.0/Makefile:957: recipe for target 'arch/powerpc/kernel' failed make[2]: *** [arch/powerpc/kernel] Error 2 We do not believe this is due to a kernel change as the code in question has not changed in years. Additionally, we had 4.0 based test builds successfully passing in our PPA (ppa:canonical-kernel- team/ppa). The last successful test build in our PPA was from May 21 (the logs are still there if needed). We were also unable to reproduce by cross-compiling. As added information, our wily kernel git repo can be seen at: https://git.launchpad.net/~ubuntu- kernel/ubuntu/+source/linux/+git/wily Let us know if any additional information is required to debug this. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: binutils 2.25-8ubuntu1 ProcVersionSignature: Ubuntu 4.0.0-1.1-generic 4.0.5 Uname: Linux 4.0.0-1-generic x86_64 ApportVersion: 2.17.3-0ubuntu4 Architecture: amd64 CurrentDesktop: Unity Date: Wed Jun 10 06:16:10 2015 Dependencies: gcc-5-base 5.1.1-9ubuntu2 libc6 2.21-0ubuntu4 libgcc1 1:5.1.1-9ubuntu2 multiarch-support 2.21-0ubuntu4 zlib1g 1:1.2.8.dfsg-2ubuntu1 EcryptfsInUse: Yes InstallationDate: Installed on 2014-03-17 (449 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140317) SourcePackage: binutils UpgradeStatus: Upgraded to wily on 2015-05-28 (12 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1463836/+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 1244438] Re: EOL notification system required for HWE kernels in LTSs
** Changed in: landscape (Ubuntu) Status: Confirmed => Won't Fix ** Changed in: linux (Ubuntu) Status: Triaged => Fix Released ** Changed in: nagios-plugins (Ubuntu) Status: Triaged => Won't Fix ** Changed in: unattended-upgrades (Ubuntu) Status: Confirmed => Won't Fix ** Changed in: update-manager (Ubuntu) Status: Confirmed => Fix Released ** Changed in: update-motd (Ubuntu) Status: Confirmed => Fix Released ** Changed in: ubuntu-release-notes Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1244438 Title: EOL notification system required for HWE kernels in LTSs Status in Release Notes for Ubuntu: Fix Released Status in landscape package in Ubuntu: Won't Fix Status in linux package in Ubuntu: Fix Released Status in nagios-plugins package in Ubuntu: Won't Fix Status in unattended-upgrades package in Ubuntu: Won't Fix Status in update-manager package in Ubuntu: Fix Released Status in update-motd package in Ubuntu: Fix Released Bug description: We need to have some mechanism to allow us to record that you have an EOL kernel installed which will no longer receive updates. For example for the kernel when a kernel is going EOL the last upload should include an appropriate file: /var/lib/update-notifier/kernel-eol We need to coordinate this with the notifier itself to ensure it is displayed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/1244438/+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
