** Tags added: reboot-required
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1747499
Title:
98-reboot-required and Interaction with livepatch
To manage notifications about this bug go to:
The package FTBFS against -proposed but builds successfully against the
-release pocket.
Based on the error, it seems related to recent changes in how apt
determines kernels that can be autoremoved.
apt (2.0.7) focal; urgency=medium
* Revert "Protect currently running kernel at run-time"
*
Trying to validate this upload but unattended-upgrades failed to build
with:
Applying pinning: PkgFilePin(id=0, priority=-32768)
Applying pin -32768 to package_file: >/test/root.unused-deps/var/lib/apt/lists/archive.ubuntu.com_ubuntu_dists_lucid-updates_main_binary-amd64_Packages'
Hello Andreas, or anyone else affected,
Accepted update-notifier into focal-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/update-
notifier/3.192.30.11 in a few hours, and then in the -proposed
repository.
Please help us by testing this new package.
Moving the packages to Fix Released since the patches were already in
Jammy:
update-notifier - fixed in 3.192.47:
http://changelogs.ubuntu.com/changelogs/pool/main/u/update-
notifier/update-notifier_3.192.54/changelog
unattended-upgrades - fixed in 2.8ubuntu1:
Thank you for the patches Olivier! LGTM, I've sponsored it for both
affected packages.
The only thing I needed to change is the version string for unattended-
upgrades 2.3ubuntu1 -> 2.3ubuntu0.2 (as this is an SRU,
https://wiki.ubuntu.com/SecurityTeam/UpdatePreparation#Update_the_packaging)
**
** Tags added: fr-1788
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1747499
Title:
98-reboot-required and Interaction with livepatch
To manage notifications about this bug go to:
** Also affects: update-notifier (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: unattended-upgrades (Ubuntu Focal)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Description changed:
+
+ [Impact]
+
+ * If a system is using canonical livepatch, has it enabled, and patches
+ are applied, it could be confusing for a user to receive a "system
+ restart required" messages in the MOTD when logging in.
+
+ * Livepatch is available on LTS releases. Thus,
The attachment "debdiff for unattended-upgrades (focal)" seems to be a
debdiff. The ubuntu-sponsors team has been subscribed to the bug report
so that they can review and hopefully sponsor the debdiff. If the
attachment isn't a patch, please remove the "patch" flag from the
attachment, remove
** Patch added: "debdiff for update-notifier (focal)"
https://bugs.launchpad.net/ubuntu/+source/update-notifier/+bug/1747499/+attachment/5583992/+files/1-update-notifier-3.192.30.10.3.192.30.11.debdiff
** Changed in: unattended-upgrades (Ubuntu)
Status: New => Confirmed
--
You
** Patch added: "debdiff for unattended-upgrades (focal)"
https://bugs.launchpad.net/ubuntu/+source/update-notifier/+bug/1747499/+attachment/5583991/+files/1-unattended-upgrades-2.3ubuntu0.1-2.3ubuntu1.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs,
** Also affects: unattended-upgrades (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1747499
Title:
98-reboot-required and Interaction with
Chiming in a a potential customer:
I can't figure out how to check when a reboot is required when using
livepatch. For example, at the moment a machine I'm testing on has only
"linux-base" in /var/run/reboot-required.pkgs.
Livepatch status says: "patch state: ✓ no livepatches needed for this
I think the problem is that external tools just simplistically look at
/var/run/reboot-required to decide whether to reboot and I don't think
we can expect them to be fixed just to handle livepatch.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
** Attachment added: "Suggested flowchart of how the decision to reboot should
be when using livepatch"
https://bugs.launchpad.net/ubuntu/+source/update-notifier/+bug/1747499/+attachment/5390197/+files/livepatch-flowchart-davecore-suggestion.png
--
You received this bug notification because
Here are some extra details about the status of livepatch when a kernel
upgrade is required.
I am running an 18.04 VM with an old 4.15.0-20-generic kernel from April
2018. Here is status in yaml format:
ubuntu@bioniclivepatcholdkernel:~$ canonical-livepatch status --format yaml
client-version:
I agree with comment #4.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1747499
Title:
98-reboot-required and Interaction with livepatch
To manage notifications about this bug go to:
Actually, I think there's more to it. Here are some thoughts
1. The compelling use case for livepatch is in fact to minimize and
control the need to reboot; this is what customers pay us for. For many
of them, rebooting every 3 weeks is either impossible or at least very
painful. Let's not lose
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: update-notifier (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1747499
I think we can agree that the MOTD messaging gets confusing. The best
way to fix it is the question.
For example, we go from this:
(...)
*** System restart required ***
* Canonical Livepatch is available for installation.
- Reduce system reboots and improve kernel security. Activate at:
The position of the Security Team has been consistent that kernel live
patching allows users to defer reboots, it does not allow users to avoid
them. Because not all security fixes are included in live patches, and
because correlating the live patch CVEs to the kernel deb CVEs requires
knowledge
22 matches
Mail list logo
