[Group.of.nepali.translators] [Bug 1896024] Re: xenial/linux-azure: 4.15.0-1097.107~16.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: Fix Released => In Progress -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1896024 Title: xenial/linux-azure: 4.15.0-1097.107~16.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow stakeholder-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux-azure source package in Xenial: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1896026 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Testing phase-changed: Friday, 25. September 2020 07:17 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: xenial/linux-azure/azure-kernel: bug 1896023 variant: debs versions: main: 4.15.0-1097.107~16.04.1 meta: 4.15.0.1097.91 signed: 4.15.0-1097.107~16.04.1 To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1896024/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1896063] Re: xenial/linux-snapdragon: 4.4.0-1144.153 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: Fix Released => In Progress -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1896063 Title: xenial/linux-snapdragon: 4.4.0-1144.153 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: In Progress Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux-snapdragon source package in Xenial: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1897734 packages: main: linux-snapdragon meta: linux-meta-snapdragon phase: Testing phase-changed: Tuesday, 22. September 2020 12:42 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: xenial/linux-snapdragon/dragonboard-kernel: bug 1896062 variant: debs versions: main: 4.4.0-1144.153 meta: 4.4.0.1144.136 To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1896063/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1896061] Re: xenial/linux-raspi2: 4.4.0-1140.149 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: Fix Released => In Progress -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1896061 Title: xenial/linux-raspi2: 4.4.0-1140.149 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: In Progress Status in Kernel SRU Workflow certification-testing series: In Progress Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux-raspi2 source package in Xenial: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1897734 packages: main: linux-raspi2 meta: linux-meta-raspi2 phase: Testing phase-changed: Tuesday, 22. September 2020 12:42 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: certification-testing: Ongoing -- testing in progress security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: xenial/linux-raspi2/pi2-kernel: bug 1896060 variant: debs versions: main: 4.4.0-1140.149 meta: 4.4.0.1140.140 To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1896061/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1895160] Re: Backport finalrd 6 to xenial and up
** Changed in: finalrd (Ubuntu Xenial) Status: Triaged => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1895160 Title: Backport finalrd 6 to xenial and up Status in finalrd package in Ubuntu: Fix Released Status in finalrd source package in Xenial: Fix Released Status in finalrd source package in Bionic: Fix Released Status in finalrd source package in Focal: Fix Released Bug description: [Impact] * finalrd is a useful tool, that improves ability to cleanly shut down systems. It is now desired to backport it all the way back to xenial. On classic systems it will not be installed by default, but available for users to opt-in into having it. On Ubuntu Core systems it will be installed by default, and used instead of snap-shutdown. As finalrd does everything that snap-shutdown already did, and much more. * finalrd is only tweaked slightly in version 6 to be compatible with any systemd from xenial to groovy. [Test Case] Classic * Install finalrd * execute `sudo finalrd` and observe that no stderr is printed, and command exits successfully * check that /run/initramfs is created and populated with /run/initramfs/shutdown, binaries and libraries. * Reboot * Observe that finalrd unit is started ** (optional) to make observing finalrd easier add /etc/finalrd/echo.finalrd hook that does `echo $@` with a sleep * Shutdown, capture console-log observe that finalrd was executed [xenial extra testcase] * finalrd binary package should have Task: ubuntu-core, such that when building core snap, it is installed by livebuild. Core * Create custom core, core18 with finalrd preinstalled * Building custom Ubuntu Core 16 and Ubuntu Core 18 image with above core * Observe that finalrd unit is started on boot * Shutdown, capture console-log observe that finarld was executed. * Boot again * execute `sudo finalrd` and observe that no stderr is printed, and command exits successfully * check that /run/initramfs is created and populated with /run/initramfs/shutdown, binaries and libraries. [Regression Potential] * Packaging & tmpfiles were changed to be compatible with older systemd versions. There are no changes to api/abi of the systemd units, or .finalrd hooks. The package is not installed by default on xenial/bionic, hence the number and type of machines affected is small. If regressions are identified, reverting to previous version of the package is safe course of action, as there are no upgrade/downgrade incompatibilities between old & new versions of finalrd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/finalrd/+bug/1895160/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1896638] Re: Path to swapfile doesn't use a static device path
** Changed in: ec2-hibinit-agent (Ubuntu Focal) Status: New => Invalid ** Changed in: ec2-hibinit-agent (Ubuntu Groovy) Status: New => Invalid ** Changed in: ec2-hibinit-agent (Ubuntu Bionic) Status: New => Confirmed ** Changed in: ec2-hibinit-agent (Ubuntu Focal) Status: Invalid => Confirmed ** Changed in: ec2-hibinit-agent (Ubuntu Groovy) Status: Invalid => Confirmed -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1896638 Title: Path to swapfile doesn't use a static device path Status in ec2-hibinit-agent package in Ubuntu: Confirmed Status in ec2-hibinit-agent source package in Xenial: New Status in ec2-hibinit-agent source package in Bionic: Confirmed Status in ec2-hibinit-agent source package in Focal: Confirmed Status in ec2-hibinit-agent source package in Groovy: Confirmed Bug description: When the agent inserts the resume device path and offset into the kernel cmdline, it uses device names such as the following: `resume_offset=223232 resume=/dev/nvme1n1p1` The issue is that `/dev/nvme1n1p1` is not static. On the reboot, the block device may appear at `/dev/nvme0n1p1` resulting in failure to find the swapfile used to suspend. The solution should be to use a persistent block device naming scheme. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ec2-hibinit-agent/+bug/1896638/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1898087] Re: Please disable suspend when the package is installed
Should this be back-ported to Bionic and Xenial, too? ** Also affects: ec2-hibinit-agent (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: ec2-hibinit-agent (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: ec2-hibinit-agent (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: ec2-hibinit-agent (Ubuntu Xenial) Status: New => Incomplete ** Changed in: ec2-hibinit-agent (Ubuntu Bionic) Status: New => Incomplete ** Changed in: ec2-hibinit-agent (Ubuntu Focal) Status: New => In Progress ** Changed in: ec2-hibinit-agent (Ubuntu) Status: Confirmed => In Progress ** Changed in: ec2-hibinit-agent (Ubuntu Focal) Status: In Progress => Confirmed -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1898087 Title: Please disable suspend when the package is installed Status in ec2-hibinit-agent package in Ubuntu: In Progress Status in ec2-hibinit-agent source package in Xenial: Incomplete Status in ec2-hibinit-agent source package in Bionic: Incomplete Status in ec2-hibinit-agent source package in Focal: Confirmed Bug description: From LP: #1892728 We also need to set "AllowSuspend=no" in /etc/systemd/sleep.conf (or a .d file) as CONFIG_SUSPEND has been disabled in the kernel to improve the robustness of hibernation. [Test Case] Try to suspend the system as a regular user: $ /lib/systemd/systemd-sleep suspend Sleep mode "suspend" is disabled by configuration, refusing. On a system where this change is not present permission error appears: $ /lib/systemd/systemd-sleep suspend Failed to open /sys/power/state: Permission denied To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ec2-hibinit-agent/+bug/1898087/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1895160] Re: Backport finalrd 6 to xenial and up
finalrd is now seeded into system-image in xenial. But because it is a brand new package in -updates pocket only, it doesn't gain Task: ubuntu- core, as that is only done for packages that exist in release pocket. Thus adding Task:ubuntu-core by hand. ** Description changed: [Impact] - * finalrd is a useful tool, that improves ability to cleanly shut down + * finalrd is a useful tool, that improves ability to cleanly shut down systems. It is now desired to backport it all the way back to xenial. On classic systems it will not be installed by default, but available for users to opt-in into having it. On Ubuntu Core systems it will be installed by default, and used instead of snap-shutdown. As finalrd does everything that snap-shutdown already did, and much more. - * finalrd is only tweaked slightly in version 6 to be compatible with + * finalrd is only tweaked slightly in version 6 to be compatible with any systemd from xenial to groovy. [Test Case] Classic - * Install finalrd - * execute `sudo finalrd` and observe that no stderr is printed, and command exits successfully - * check that /run/initramfs is created and populated with /run/initramfs/shutdown, binaries and libraries. - * Reboot - * Observe that finalrd unit is started - ** (optional) to make observing finalrd easier add /etc/finalrd/echo.finalrd hook that does `echo $@` with a sleep - * Shutdown, capture console-log observe that finalrd was executed + * Install finalrd + * execute `sudo finalrd` and observe that no stderr is printed, and command exits successfully + * check that /run/initramfs is created and populated with /run/initramfs/shutdown, binaries and libraries. + * Reboot + * Observe that finalrd unit is started + ** (optional) to make observing finalrd easier add /etc/finalrd/echo.finalrd hook that does `echo $@` with a sleep + * Shutdown, capture console-log observe that finalrd was executed + + [xenial extra testcase] + + * finalrd binary package should have Task: ubuntu-core, such that when + building core snap, it is installed by livebuild. Core - * Create custom core, core18 with finalrd preinstalled - * Building custom Ubuntu Core 16 and Ubuntu Core 18 image with above core - * Observe that finalrd unit is started on boot - * Shutdown, capture console-log observe that finarld was executed. - * Boot again - * execute `sudo finalrd` and observe that no stderr is printed, and command exits successfully - * check that /run/initramfs is created and populated with /run/initramfs/shutdown, binaries and libraries. + * Create custom core, core18 with finalrd preinstalled + * Building custom Ubuntu Core 16 and Ubuntu Core 18 image with above core + * Observe that finalrd unit is started on boot + * Shutdown, capture console-log observe that finarld was executed. + * Boot again + * execute `sudo finalrd` and observe that no stderr is printed, and command exits successfully + * check that /run/initramfs is created and populated with /run/initramfs/shutdown, binaries and libraries. [Regression Potential] - * Packaging & tmpfiles were changed to be compatible with older systemd + * Packaging & tmpfiles were changed to be compatible with older systemd versions. There are no changes to api/abi of the systemd units, or .finalrd hooks. The package is not installed by default on xenial/bionic, hence the number and type of machines affected is small. If regressions are identified, reverting to previous version of the package is safe course of action, as there are no upgrade/downgrade incompatibilities between old & new versions of finalrd. ** Changed in: finalrd (Ubuntu Xenial) Status: Fix Released => Triaged -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1895160 Title: Backport finalrd 6 to xenial and up Status in finalrd package in Ubuntu: Fix Released Status in finalrd source package in Xenial: Triaged Status in finalrd source package in Bionic: Fix Released Status in finalrd source package in Focal: Fix Released Bug description: [Impact] * finalrd is a useful tool, that improves ability to cleanly shut down systems. It is now desired to backport it all the way back to xenial. On classic systems it will not be installed by default, but available for users to opt-in into having it. On Ubuntu Core systems it will be installed by default, and used instead of snap-shutdown. As finalrd does everything that snap-shutdown already did, and much more. * finalrd is only tweaked slightly in version 6 to be compatible with any systemd from xenial to groovy. [Test Case] Classic * Install finalrd * execute `sudo finalrd` and observe that no stderr is printed, and command exits successfully * check that /run/initramfs is created and populated wi
