Repository navigation
Debian kernel security update is kept back but device is reported as Fully Patched #30
Replies: 5 comments
|
Confirmed again on RemotePower Agent 7.0.3 / Ubuntu 24.04. The same issue now occurs with linux-firmware. apt-get -s upgrade --with-new-pkgs correctly resolves it: 1 upgraded, 18 newly installed, 0 to remove and 0 not upgraded. The agent still executes plain apt-get -y upgrade, returns rc=0, and leaves the package pending. So this is not Debian/kernel-specific; the same behavior reproduces on Ubuntu 24.04 with the new split linux-firmware packaging. |
|
Thanks for the report and the exact commands, and sorry this sat unanswered for so long. You were right, and your Ubuntu 24.04 follow-up shows it is not specific to Debian or to kernels. The agent counts the packages that We went with your second option: detect what apt keeps back and keep the host pending. The fix is written and tested, and it is not in a release yet. We have checked it against the output you posted and against stand-in apt programs. We have not yet run it on a real Debian or Ubuntu host, so please tell us if it does not match what you see.
We will say here when it is in a pre-release you can try. |
|
It is in v7.4.8, which is on the It works as described above. A package apt keeps back counts as pending, and as a security update when apt lists it from a security archive. A package held with The agent does the counting, so the agent on the host has to be the 7.4.8 one. After the server is updated, agents pick it up within about an hour, or at once with We have still not run this on a real Debian or Ubuntu host, and your Ubuntu 24.04 host with the Two things are still open:
To try it, back up your data volume first, then: Download. The signed tarball is on the pre-release page, with a Docker. Build one from the tag ( Bare metal. |
|
Thank you for the detailed explanation and for addressing this issue in v7.4.8! Unfortunately, I'm currently unable to test the pre-release on a real Debian or Ubuntu host, as all of my servers are running in production. I'd prefer not to risk the stability of these systems by deploying a development build. I'll try to verify the fix and share the results when I have a safe opportunity to do so. Regarding It would be great if RemotePower could offer two upgrade modes:
Ideally, this should be configurable for both the manual Patch button and Auto-Patch, with the option to select the preferred mode individually for each host. The standard mode could remain the default to preserve backward compatibility. I think this is particularly important for security updates. If RemotePower detects a pending security update, it would be useful to have the option to install it directly through the dashboard without having to SSH into the host manually. Thanks again for your work on the project and for taking the time to investigate our report! |
|
Hi @KILLERPsix, 7.5.0 is out as a stable release, so you can try this without putting a pre-release on your production hosts. It comes as a signed tarball and as Docker images for the server and the agent ( The two modes you described are in. Standard is still the default and does what The detection from 7.4.8 is part of it too. A package apt keeps back counts as pending, and as a security update when apt lists it from a security archive; the host's drawer names it, and a package held with The agent does the counting, so the agents need the update as well. They pick it up within about an hour of the server update, or right away with On your Ubuntu 24.04 host with the |
Uh oh!
There was an error while loading. Please reload this page.
Hi,
I think I found an issue with patch status detection on Debian.
Environment
7.0.2Debian GNU/Linux 13 (trixie)aptProblem
RemotePower reports the device as:
Fully PatchedPending: 0At the same time, the CVE view reports 63 fixable CVEs.
The host has a pending Debian security kernel update:
RemotePower executes:
However, on this host:
returns:
The package is not manually held:
This returns no packages.
However:
correctly detects the update:
Actual behavior
apt-get upgradeexits successfully withrc=0, but leaves the kernel security update askept back.RemotePower then reports the device as:
Fully PatchedPending: 0even though the security update is still available.
Expected behavior
RemotePower should not report the device as
Fully Patchedwhile APT still has a security update kept back.Possible options could be:
apt-get upgrade --with-new-pkgsfor Debian/Ubuntu;kept back/not upgradedpackages after the upgrade command and keep the device in a pending state.Additional symptom
The Patch Report shows the host as
Fully Patched, while the CVE subsystem reports fixable CVEs on the same device.Could you please confirm whether this is expected behavior or a bug?

All reactions