Your message dated Tue, 03 Dec 2024 14:44:01 +0000 with message-id <e1tiu89-006kg5...@fasolo.debian.org> and subject line Bug#1088012: fixed in needrestart 3.6-4+deb12u3 has caused the Debian Bug report #1088012, regarding needrestart does not have sufficient information to restart LXC containers to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 1088012: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1088012 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Package: needrestart Version: 3.7-3.1 The new needrestart offers to restart the LXC containers it has found somehow, but then it fails for a more complex scenario. Sample session: # -------------------------------------------------------------------------- root@srvl033a:~# needrestart -u NeedRestart::UI::stdio Scanning processes... Scanning candidates... Scanning processor microcode... Scanning linux images... Pending kernel upgrade! Running kernel version: 6.10.11+bpo-amd64 Diagnostics: The currently running kernel version is not the expected kernel version 6.11.5+bpo-amd64. Restarting the system to load the new kernel will not be handled automatically, so you should consider rebooting. [Return] The processor microcode seems to be up-to-date. Restarting services... Services to be restarted: Restart «dbus.service»? [yNas?] Restart «getty@tty1.service»? [yNas?] Restart «lxc»? [yNas?] Restart «lxc-monitord.service»? [yNas?] Restart «lxc-net»? [yNas?] Restart «serial-getty@ttyS0.service»? [yNas?] Restart «systemd-logind.service»? [yNas?] Restart «unattended-upgrades.service»? [yNas?] Service restarts being deferred: /etc/needrestart/restart.d/dbus.service systemctl restart getty@tty1.service systemctl restart lxc.service systemctl restart lxc-monitord.service systemctl restart lxc-net.service systemctl restart serial-getty@ttyS0.service systemctl restart systemd-logind.service systemctl restart unattended-upgrades.service Restarting containers... Containers to be restarted: Restart «LXC debian10»? [Ynas?] lxc-stop --reboot --name debian10 lxc-stop: debian10: ../src/lxc/tools/lxc_stop.c: lxc_stop_main: 169 debian10 is not running Restart «LXC nfs00»? [Ynas?] lxc-stop --reboot --name nfs00 lxc-stop: nfs00: ../src/lxc/tools/lxc_stop.c: lxc_stop_main: 169 nfs00 is not running Restart «LXC sample1a»? [Ynas?] lxc-stop --reboot --name sample1a lxc-stop: sample1a: ../src/lxc/tools/lxc_stop.c: lxc_stop_main: 169 sample1a is not running Restart «LXC sample1c»? [Ynas?] lxc-stop --reboot --name sample1c lxc-stop: sample1c: ../src/lxc/tools/lxc_stop.c: lxc_stop_main: 169 sample1c is not running No user sessions are running outdated binaries. No VM guests are running outdated hypervisor (qemu) binaries on this host. # -------------------------------------------------------------------------- Without knowing(!) the path of the container config files restarting the LXC containers is dangerous. Its easy to start a second instance by accident, or to fail, as shown above. A wild guess, /var/lib/lxc/name/config must be the right file, if it exists, would be fatal. needrestart has to obtain the path to the right, unmodified config file path from LXC, if the container is already running. Regards Harri
--- End Message ---
--- Begin Message ---Source: needrestart Source-Version: 3.6-4+deb12u3 Done: Salvatore Bonaccorso <car...@debian.org> We believe that the bug you reported is fixed in the latest version of needrestart, which is due to be installed in the Debian FTP archive. A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to 1088...@bugs.debian.org, and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Salvatore Bonaccorso <car...@debian.org> (supplier of updated needrestart package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmas...@ftp-master.debian.org) -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Format: 1.8 Date: Mon, 02 Dec 2024 20:52:03 +0100 Source: needrestart Architecture: source Version: 3.6-4+deb12u3 Distribution: bookworm-security Urgency: high Maintainer: Patrick Matthäi <pmatth...@debian.org> Changed-By: Salvatore Bonaccorso <car...@debian.org> Closes: 1087917 1087918 1087957 1087958 1088012 1088047 Changes: needrestart (3.6-4+deb12u3) bookworm-security; urgency=high . * Non-maintainer upload by the Security Team. * core: fix regression of false positives for processes running in chroot or mountns (Closes: #1087918, #1088047, #1088012, #1087917, #1087958, #1087957) Checksums-Sha1: d24c4364bb8a3451e5e33c28572bb7afca605726 2007 needrestart_3.6-4+deb12u3.dsc 34c7b6f22b04a0861eadef0e563aacca02cd7cbd 15952 needrestart_3.6-4+deb12u3.debian.tar.xz Checksums-Sha256: fb14a954e5d64c0e3789d172efd1320275277332a85809c9304e203adf70f3f3 2007 needrestart_3.6-4+deb12u3.dsc 406b9f8e020f8a181cfc2087dfdf01dc858bbac7bd9ea44e57351054e25592db 15952 needrestart_3.6-4+deb12u3.debian.tar.xz Files: e4dbddf5ffec42f6a111fab41b469152 2007 admin optional needrestart_3.6-4+deb12u3.dsc 426ffbbbc4c7c6d3f0b6cffe8d8efde4 15952 admin optional needrestart_3.6-4+deb12u3.debian.tar.xz -----BEGIN PGP SIGNATURE----- iQKmBAEBCgCQFiEERkRAmAjBceBVMd3uBUy48xNDz0QFAmdOEKZfFIAAAAAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDQ2 NDQ0MDk4MDhDMTcxRTA1NTMxRERFRTA1NENCOEYzMTM0M0NGNDQSHGNhcm5pbEBk ZWJpYW4ub3JnAAoJEAVMuPMTQ89EWvAP/iyBdJxrzZr8nB4aQTq9w5MmTd2D9Duc cUv+VeUeuVklv3TpD+knfVAe+R3ckCd9+9VBZFo8zzZPQ7FmpknUzzzK5dWKaQjc ce86cnrvj4hJ4Ln5famBw52R4vrvXCbxi0k7RuJbTvEo4yz0J+V3vUoGv0BHtxCp 0jVXJcyPDJzDFr647ZPMRk+nVOKaNmnQO6FtTl2BdD2tH2xjNtWlRIp0xQpfJTfj JjymM5GzfsZjGPzK9vSIOrdCkwmf9SNe5yj4f/ECwXc27ifvbRD8K47TqDrE2A4+ sIK5hwEdEChvxlMtwbDlIu/ib+EIqvYhutSOlngo4OMR04p2nTiy/JFpQv9oKMLD Xlc4HX6b+XPQeGqIarsEPeVad+s0034WsIu8nt3BFmbFH+vCN5X7QeVklTHQNFt/ Cfj7ljgXEwon/v2GG78KXeSmYTtSvp9VAsJGfic+NK8R7J5UN+OdlL6X40nQmqdl GE87FmaNZDSiP6KHLfmziS2XQmcDZ9ADVkowYzgq+MhcdUmzGsJHVg5mbNukEmM5 gMefGQHO0N1RtNHKv2WVf83EWtIb9nm3sSUhJFkmrpoaNO1WIlGzhIjEaCNPge1m 4LJGPFaFD8hKLZXq7Nc4yQP5XfAKaHi+FwrRFafMe4OHZ27Hntst0rr+q9rqxoM/ 3fTF6fSi28SY =aEla -----END PGP SIGNATURE-----
pgp9GPb6d9P9H.pgp
Description: PGP signature
--- End Message ---
