On Wed, 29 Oct 2025 00:47:22 +0100 Matija Nalis <[email protected]> wrote: > Hi Jan, > > > I belive this should be fixed in Proxmox. > > OK, I've reported it to proxmox at > https://bugzilla.proxmox.com/show_bug.cgi?id=6981 > > > There are many other situations where 3rd party kernel images > > can/are used and potentially this can break the version detection. > > Which is why this patch was written in such a way to avoid such > possible breakages (i.e. it would only trigger if the versions are > completely the same, except on-disk one having empty " ()" section at > the end. That should not make any false positives or break any other > detections). > > > I'm still open for a more general solution. > > More general solution might be to remove such empty section > (whitespace plus empty parenthsesis) anywhere in the version string. > That could be done in "on_disk_version" to be in more proper place, > as you suggested. > > But let's see what Proxmox people will reply first.
Hi! The discrepancy seems to stem from CONFIG_VERSION_SIGNATURE not being set in our kernel builds. While we can of course enable this, this alone would not fix the nagios check. AFAICT (without setting up a full reproducer, just looking at the script!) the script should use `/proc/version_signature` to obtain the value for stripping from the currently booted kernel, to compare whether the on-disk version is identical to the booted one, instead of assuming the value of CONFIG_VERSION_SIGNATURE has to match "`lsb-release -i -s` ..." Regards, Fabian
