Closed MAGICCC closed 7 years ago
The Reboot flag depends on the result of apt-dater-host on the target server which uses needrestart to check for outdated kernels. Since Ubuntu picks apt-dater and needrestart packages w/o any QA they are often somehow broken.
So tl;dr this output can't be used for 'hey please reboot me' anymore
It can, but you need to have a reasonable apt-dater-host+needrestart versions on the targets where Ubuntu is known to have QA problems.
So, is there anything that can be done about this? I tried grabbing newer versions of apt-dater-host and needrestart from launchpad (the ones for zesty/16.10), which appear to match the versions I'm running on Debian 9, but the R flag does not go away.
These are what I downloaded and installed: https://launchpad.net/ubuntu/+archive/primary/+files/needrestart_2.11-2_all.deb https://launchpad.net/ubuntu/+archive/primary/+files/apt-dater-host_1.0.0-4_all.deb
The output from running the 'needrestart' command appears to match what my Debian systems display, but apt-dater still complains that it needs a reboot.
Hi,
I installed apt-dater on my VMs today, but after install kernel updates and rebooting the VMs apt-dater is still saying that I should reboot my VMs...