summaryrefslogtreecommitdiff
path: root/python/setup.py
diff options
context:
space:
mode:
authorChristian Breunig <christian@breunig.cc>2026-10-18 08:35:18 +0200
committerChristian Breunig <christian@breunig.cc>2026-10-18 08:35:18 +0200
commite166e09f917d0c1c2e907c747abca34d8669acd8 (patch)
treeb19baaa368360aca9055836181ae86bb435fb0bf /python/setup.py
parentdb29bdc899e4b4c27569d3c5705839b924393fe6 (diff)
downloadvyos-1x-e166e09f917d0c1c2e907c747abca34d8669acd8.tar.gz
vyos-1x-e166e09f917d0c1c2e907c747abca34d8669acd8.zip
kdump: T8868: skip kdump-tools when no crashkernel= is set
kdump-tools runs early in boot, before the VyOS configuration renders its defaults file. On a live ISO, or on any system without "system option kdump", it therefore starts with the Debian default USE_KDUMP=1 and reports "no crashkernel= parameter in the kernel cmdline ... failed!" on the console. The service is now only started when a crashkernel= parameter is present on the kernel command line, which is exactly the case when kdump is configured. The smoketest previously expected the service to be active right after commit, which only held because the failing unit still ended up "active". It now expects the service to run only when booted with crashkernel=.
Diffstat (limited to 'python/setup.py')
0 files changed, 0 insertions, 0 deletions