)
diff --git a/AppImage/components/proxmox-dashboard.tsx b/AppImage/components/proxmox-dashboard.tsx
index b0a1c92e..a7defe21 100644
--- a/AppImage/components/proxmox-dashboard.tsx
+++ b/AppImage/components/proxmox-dashboard.tsx
@@ -814,7 +814,7 @@ export function ProxmoxDashboard() {
diff --git a/AppImage/scripts/flask_server.py b/AppImage/scripts/flask_server.py
index dbe77b47..c51ea08f 100644
--- a/AppImage/scripts/flask_server.py
+++ b/AppImage/scripts/flask_server.py
@@ -10435,7 +10435,7 @@ def api_health():
return jsonify({
'status': 'healthy',
'timestamp': datetime.now().isoformat(),
- 'version': '1.2.1.2-beta'
+ 'version': '1.2.1.3-beta'
})
# ─── User-configurable health thresholds ─────────────────────────────────────
@@ -10872,7 +10872,7 @@ def api_info():
"""Root endpoint with API information"""
return jsonify({
'name': 'ProxMenux Monitor API',
- 'version': '1.2.1.2-beta',
+ 'version': '1.2.1.3-beta',
'endpoints': [
'/api/system',
'/api/system-info',
@@ -11522,7 +11522,7 @@ if __name__ == '__main__':
try:
import sqlite3
from pathlib import Path
- MONITOR_VERSION = '1.2.1.2-beta'
+ MONITOR_VERSION = '1.2.1.3-beta'
db_path = Path('/usr/local/share/proxmenux/health_monitor.db')
if db_path.exists():
conn = sqlite3.connect(str(db_path), timeout=10)
diff --git a/AppImage/scripts/health_monitor.py b/AppImage/scripts/health_monitor.py
index 5e1413f2..9c1a0a5f 100644
--- a/AppImage/scripts/health_monitor.py
+++ b/AppImage/scripts/health_monitor.py
@@ -4177,7 +4177,21 @@ class HealthMonitor:
'pve-', 'proxmox-', 'qemu-server', 'lxc-pve', 'ceph',
'corosync', 'libpve', 'pbs-', 'pmg-',
)
- _KERNEL_PREFIXES = ('linux-image', 'pve-kernel', 'pve-firmware')
+ # Kernel-package prefixes for categorisation. Order matters: the matcher
+ # in update parsing checks KERNEL first and PVE second, so `proxmox-kernel`
+ # must appear here before the generic `proxmox-` falls through to
+ # _PVE_PREFIXES. Bug #208 — PVE 9.x ships kernels as `proxmox-kernel-*`
+ # (Debian 13 base), not `pve-kernel-*` as in older Proxmox; without the
+ # `proxmox-kernel` prefix every kernel update was mis-categorised as a
+ # generic PVE update and the dashboard reported "Kernel/PVE up to date"
+ # even with a kernel patch waiting for the running CT.
+ _KERNEL_PREFIXES = (
+ 'linux-image',
+ 'pve-kernel',
+ 'proxmox-kernel',
+ 'pve-firmware',
+ 'proxmox-firmware',
+ )
_IMPORTANT_PKGS = {
'pve-manager', 'proxmox-ve', 'qemu-server', 'pve-container',
'pve-ha-manager', 'pve-firewall', 'ceph-common',
@@ -4232,10 +4246,18 @@ class HealthMonitor:
except Exception:
pass
- # Perform a dry run of apt-get upgrade to see pending packages
+ # Perform a dry run of apt-get dist-upgrade to see pending
+ # packages. `dist-upgrade` (a.k.a. `full-upgrade`) is what the
+ # Proxmox VE web UI's Updates tab runs internally, and unlike
+ # plain `apt-get upgrade` it surfaces kernel updates packaged
+ # as NEW installs (e.g. `proxmox-kernel-6.14.11-9-pve-signed`
+ # showing up as `Inst` when the running CT is on -4). Bug #208
+ # — without dist-upgrade these updates never appeared in the
+ # `Inst` list at all, so the Kernel/PVE sub-check stayed
+ # green even when the running kernel had a patch waiting.
try:
result = subprocess.run(
- ['apt-get', 'upgrade', '--dry-run'],
+ ['apt-get', 'dist-upgrade', '--dry-run'],
capture_output=True, text=True, timeout=30
)
except subprocess.TimeoutExpired:
@@ -4252,18 +4274,42 @@ class HealthMonitor:
security_pkgs: list = []
kernel_pkgs: list = []
pve_pkgs: list = []
+ running_kernel_pkgs: list = [] # {name, cur, new} — kernel(s) matching `uname -r`
important_pkgs: list = [] # {name, cur, new}
pve_manager_info = None # {cur, new} or None
sec_result = None
sec_severity = 'INFO'
sec_days_unpatched = 0
-
+
+ # Read the running kernel release (e.g. `7.0.2-5-pve`) so we can
+ # distinguish a kernel update that REPLACES the kernel the host
+ # is currently booted from (urgent, requires reboot) from one
+ # that only touches an older kernel still present in the
+ # bootloader or the meta-package pointers. Bug #208.
+ #
+ # `running_kernel_branch` extracts the major.minor branch from
+ # the running release — e.g. `7.0.2-5-pve` → `7.0`. We use it
+ # to detect updates to the branch META package
+ # (`proxmox-kernel-7.0` / `pve-kernel-7.0`), which when
+ # upgraded pull in the latest kernel of that branch and so
+ # also replace the running kernel on the next boot.
+ running_kernel = ''
+ running_kernel_branch = ''
+ try:
+ running_kernel = os.uname().release
+ rk_low = running_kernel.lower()
+ m = re.match(r'^(\d+\.\d+)', rk_low)
+ if m:
+ running_kernel_branch = m.group(1)
+ except Exception:
+ pass
+
if result.returncode == 0:
for line in result.stdout.strip().split('\n'):
if not line.startswith('Inst '):
continue
update_count += 1
-
+
# Parse package name, current and new versions
m = self._RE_INST.match(line)
if m:
@@ -4276,18 +4322,56 @@ class HealthMonitor:
parts = line.split()
pkg_name = parts[1] if len(parts) > 1 else 'unknown'
cur_ver, new_ver = '', ''
-
+
# Strip arch suffix (e.g. package:amd64)
pkg_name = pkg_name.split(':')[0]
name_lower = pkg_name.lower()
line_lower = line.lower()
-
+
# Categorise
if 'security' in line_lower or 'debian-security' in line_lower:
security_pkgs.append(pkg_name)
-
+
if any(name_lower.startswith(p) for p in self._KERNEL_PREFIXES):
kernel_pkgs.append(pkg_name)
+ # Does this package match the currently running
+ # kernel? Proxmox kernels are named
+ # `proxmox-kernel-