PSA: There's a problem with Debian release 12.3 - suggested not to update right away! reddit / selfhosted ---------------------------------------------------------------------- ScratchinCommander · 2023-12-10 21:54 "Due to an issue in ext4 with data corruption in kernel 6.1.64-1, we are pausing the 12.3 image release for today while we attend to fixes. Please do not update any systems at this time, we urge caution for users with UnattendedUpgrades configured. Please see bug# 1057843: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1057843" ---------------------------------------------------------------------- fprof · 2023-12-11 00:26 Already fixed. ---------------------------------------------------------------------- thekrautboy · 2023-12-11 00:45 Afaik its fixed upstream but not yet released, right? ---------------------------------------------------------------------- ScratchinCommander · 2023-12-11 00:46 12.4 did get released ---------------------------------------------------------------------- thekrautboy · 2023-12-11 00:46 *"automatic upgrades are fine and never cause any real problems!"...* ---------------------------------------------------------------------- Other-Technician-718 · 2023-12-11 00:48 I had that affected kernel on one of my VMs, other VMs had error messages regarding the source - because it was removed already. Package was afair linux-image-6.1.0-14-amd64 that was removed. I rolled my VM back to linux-image-6.1.0-13-amd64 ---------------------------------------------------------------------- thekrautboy · 2023-12-11 00:49 Yes about 5h ago already so i guess this thread was pointless? https://www.reddit.com/r/debian/comments/18fb3v2 ---------------------------------------------------------------------- ScratchinCommander · 2023-12-11 01:32 I guess yeah ---------------------------------------------------------------------- epsiblivion · 2023-12-11 03:55 proxmox 8.1.3 kernel is on 6.2.16-19 ---------------------------------------------------------------------- thekrautboy · 2023-12-11 04:25 You cannot directly equate kernel version numbering between proxmox and debian. Proxmox uses a custom kernel with slightly different versioning. ---------------------------------------------------------------------- dschaper · 2023-12-11 04:55 Unattended upgrade works a treat. Looks like a kernel issue so you'd need to reboot for it to bite you. I wouldn't reboot unattended even if I was doing a manual update/upgrade. ---------------------------------------------------------------------- thekrautboy · 2023-12-11 04:59 And do you feel the same when people use things like Watchtower and have it set to auto-update every new Pihole release? ;) ---------------------------------------------------------------------- dschaper · 2023-12-11 05:03 I have watchtower set on my own systems to update containers that are okay going down if there's an issue. I have Pi-hole set to notify me so I can update when I am able to intervene, exactly like handling a kernel update with unattended upgrades. You can do whatever floats your dinghy, I prefer to use the available tools in a way that helps me instead of shooting myself in the foot and then blaming the gun. ---------------------------------------------------------------------- thekrautboy · 2023-12-11 05:07 Sure and i agree with that. To me auto-upgrading OS packages or other essential things like Pihole (or any other DNS) is shooting myself in the foot :) I would be okay with auto-updating less essential things and i admit i usually have diun set to notify me of any container updates, but when they have added up over a few days or so i dont always take the time and look at each images releasenotes and instead just use dockcheck to update a entire host. But always excluding any critical services. ---------------------------------------------------------------------- dschaper · 2023-12-11 05:12 You ever look at unattended upgrades and see how configurable it is? Security updates can't wait with zero days... Again, do what you feel works for you but don't just blame the tools because you don't know how to use them effectively. ---------------------------------------------------------------------- thekrautboy · 2023-12-11 05:15 Thanks i am aware :) ---------------------------------------------------------------------- Cylian91460 · 2023-12-11 08:25 Another reason why arch of better ---------------------------------------------------------------------- fprof · 2023-12-11 09:00 I would recommend it to everyone. ---------------------------------------------------------------------- ScratchinCommander · 2023-12-11 10:14 btw ---------------------------------------------------------------------- GolemancerVekk · 2023-12-11 10:23 And even unattended, there's a difference between doing upgrade vs dist-upgrade – the former is not allowed to remove or install packages so it will never change your kernel. ---------------------------------------------------------------------- programmer-ke · 2023-12-11 10:28 I've set up unnattended *security* updates and enabled reboot when necessary. I'm I doing it wrong? My reasoning is that security updates are well tested, and touch only the most necessary packages. I wouldn't like to be offline for a few days and come back and find someone exploited a security issue that was newly fixed. ---------------------------------------------------------------------- braiam · 2023-12-11 11:42 I don't get it. You do not update to 12.x, the image is updated to have the latest version of the packages as to not have people download several months worth of updates. ---------------------------------------------------------------------- ScratchinCommander · 2023-12-11 12:18 If you were on 12.2, the suggestion was not to update to 12.3 because of this release issue with the Linux kernel. Shortly thereafter the Debian release team issued 12.4 with a fix (different kernel image) and so if you were to update an install on 12.2 (or 12.0/1) then it'd go straight to 12.4 ---------------------------------------------------------------------- GeekOfAllGeeks · 2023-12-11 13:19 FYI, proxmox uses the Ubuntu LTS kernel as a base with their patches on top. ---------------------------------------------------------------------- thekrautboy · 2023-12-11 14:17 Nice, that means a Debian bug like this would likely have never made it there. ---------------------------------------------------------------------- thekrautboy · 2023-12-11 14:22 Another reason to simply block people like you. ---------------------------------------------------------------------- ScratchinCommander · 2023-12-11 15:15 That's usually what I do with a few exceptions. You could also disable reboot and use the e-mail "on-change" config so you get a chance to see what has been done. You can also enable logging to syslog as well and then decide to take action/reboot manually. Not sure if the 12.3 release had any security updates associated with it, specifically the buggy kernel version. It's a risk vs reward - if you have your applications/data backed up, you should be able to recover from a failed auto-upgrade. ---------------------------------------------------------------------- ScratchinCommander · 2023-12-11 15:15 The deb team was pretty quick at least. ---------------------------------------------------------------------- thekrautboy · 2023-12-11 16:01 True ---------------------------------------------------------------------- sysop073 · 2023-12-11 18:12 Has anybody ever actually said that, because it seems extremely made up ---------------------------------------------------------------------- thekrautboy · 2023-12-11 18:15 Just browse all the watchtower etc discussions around here. While the majority of people are aware that updating everything blindly has risks, every single time this gets discussed a handful of people crawl out of the woodworks and claim "ive been using watchtower to auto update my containers for 24 years now and i never had any issues! so obviously that is proof that its fine for everyone to do the same and you guys all are wrong here!"... basically.