Open guillomovitch opened 7 months ago
Thank you for your report. This issue should be solved by this commit: https://github.com/uyuni-project/uyuni/pull/8383 It's planned to be part of the next uyuni release.
@wweellddeerr I think the PR will not address this concern. Any comment on it? thank you
The PR will only fix salt minion logs issue, not dnf logs issue, nor abusive resource usage.
A real fix would be to stop running this query every 10s, as if real-time information was required. Actualising packages list seems to be done either through a regular server-scheduled task, either immediatly after package upgrade, why not use the same principle here ?
In other distributions, the verification is as simple as checking if a given file exists or not, so running it every 10 seconds doesn't seem to be an issue. However, considering that for CentOS the verification is not as straightforward, I think we should consider increasing the verification interval to every 30 seconds or perhaps every 1 minute.
In the package list refresh, we also update the required reboot data. However, initially, we decided it would be better to constantly check if a reboot is needed directly in the system to handle any situation. You can modify the verification interval or disable it entirely by creating a custom configuration file in the system, for instance, /etc/venv-salt-minion/minion.d/custom.conf
:
beacons:
reboot_info:
interval: 120
disabled: true
If you disable the beacon, the information will be updated with every package profile update. Therefore, I believe the behavior will align with what you just described.
Indeed, this solution works. Thanks for the hint :)
@wweellddeerr do you think there's anything from our side to fix/implement?
@wweellddeerr do you think there's anything from our side to fix/implement?
@avshiliaev there is an ongoing discussion regarding the best way to resolve this problem definitively. For now, there is a PR under review increasing the beacon execution interval.
Problem description
Since Version 2024.01, Uyuni is now able to properly determine reboot required status on non-SUSE distributions, which is great.
However, it turns out this determination has undesirable side-effects, at least on CentOS distribution, as it relies on running 'needs-restarting', or 'dnf -q needs-restarting -r' depending on version, every 10 seconds. The immediate consequence is having Salt minion logs, and DNF logs overfilled with endless repeated information. And I didn't checked yet impact on other resources (CPU, memory, netowrk...).
I personnaly don't think checking every 10s is really needed, whereas just checking once after each package update would be really enough. Unfortunatly, I didn"t found any way to modify this default frequency.
Steps to reproduce
Update Uyuni to version 2024.01 Update salt-minion version to latest available (3006.0-24.11.uyuni on CentOS9, 3006.0-25.1.uyuni on CentOS 8 and CentOS 7)
Uyuni version
Uyuni proxy version (if used)
No response
Useful logs
Additional information
No response