Your message dated Wed, 27 Nov 2024 20:43:22 +0000 with message-id <e1tgosc-00d5em...@fasolo.debian.org> and subject line Bug#1088012: fixed in needrestart 3.7-3.2 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.7-3.2 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: Wed, 27 Nov 2024 20:45:40 +0100 Source: needrestart Architecture: source Version: 3.7-3.2 Distribution: unstable Urgency: medium Maintainer: Patrick Matthäi <pmatth...@debian.org> Changed-By: Salvatore Bonaccorso <car...@debian.org> Closes: 1087917 1087918 1087957 1087958 1088012 1088047 Changes: needrestart (3.7-3.2) unstable; urgency=medium . * Non-maintainer upload. * core: fix regression of false positives for processes running in chroot or mountns (Closes: #1087918, #1088047, #1088012, #1087917, #1087958, #1087957) Checksums-Sha1: 6ca587299a3b2f5c6e3bc0f0fc5943e18666132c 1983 needrestart_3.7-3.2.dsc 9e6e538dd43ea9f6d76c8e7863269f0f04a1bbad 15500 needrestart_3.7-3.2.debian.tar.xz Checksums-Sha256: 7366de19c64930e0057d17833346fc5cb46d64366b185bc11761909088dd1671 1983 needrestart_3.7-3.2.dsc 4ccc4278be120d29f96f9c2e48825b919bacf10a119170a19e0258c7f172f254 15500 needrestart_3.7-3.2.debian.tar.xz Files: f6627a68922d36b180597e51f980735f 1983 admin optional needrestart_3.7-3.2.dsc 68be43a94bc0406a2d099a7d1ea5827b 15500 admin optional needrestart_3.7-3.2.debian.tar.xz -----BEGIN PGP SIGNATURE----- iQKmBAEBCgCQFiEERkRAmAjBceBVMd3uBUy48xNDz0QFAmdHd5pfFIAAAAAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDQ2 NDQ0MDk4MDhDMTcxRTA1NTMxRERFRTA1NENCOEYzMTM0M0NGNDQSHGNhcm5pbEBk ZWJpYW4ub3JnAAoJEAVMuPMTQ89E1XQQAJDQVe1E6A0OXA/JwfBIfWRo+hKn/p9X 19UWnV/22xA06PM8p66LlgzPl/ULEmVLFpB8pN8mMoypcONiE4kFlBsFaXsNDGzE AMnbu2xIHi1idOmwrarwvLMuGYOh/TdawwMn6RUHyhZ7UWl2rYy4oDm+LSzeDd8u Qg0y0Cfe8RIQPvPbA9OMFjkcb4HSNcu14cR0+7RzIcrArhxOsg8vWNgi1aIN9JL+ B4gF3uPSUplxWy68FYfOh0/th4m8MGZbyUfwapFy4NslUR4WuoHoU0FDDtYvlcqw SWUSpN082VZMGKjDd4J3Pv/xRVfnqbKxdZh+FBzi6k8ntKS9gMylCfKQUJIU9Z6c 27eeNFbksCTDz+NpyO7TIzq5xNUsTzWfdnRJOv6KgeqLCVCRBYGUCg5wvS5LKdoe +mKUF0q2Q6/1JvXUygVnXvrDWoYvDwG+XrZwI/oFn4WYlLYA4/ROxyRW45YYPUOQ Dzw8oCLopZRTSId1Xd5fE9UdS4x4V50us+6ajzfGX6y1G+NbQceNlTZJzD8zyfXN DLiCJUaqGBnPfXdtd5fcerEyuXBjsPk1nkpZMMj8GwSdp6pykfqSQ6s3I2utUWtx TI4yYxtu1N64cpl0SxSdCK/AsofZRXEaz0eOP6QqJjCeAAJOOVsqwiTwyhPUSkA9 nZowqHP3S1lB =BhUo -----END PGP SIGNATURE-----
pgp3qDOh3MeWJ.pgp
Description: PGP signature
--- End Message ---
