Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

EL9 automatic update status isn't detected/shown correctly on private dashboard #1371

Open
athompson-merlin opened this issue Nov 1, 2023 · 1 comment

Comments

@athompson-merlin
Copy link

On an EL9 system (Alma 9, in my case) , yum-cron no longer exists, and is replaced with dnf-automatic. However, /usr/lib/perfsonar/scripts/system_environment/testpoint/enable_auto_updates still attempts to enable autopdates via yum-cron files, and the dashboard incorrectly shows "Auto Updates - OFF".

I haven't been able to find the code responsible for that, or I'd probably have a patch here, too...

@arlake228
Copy link
Contributor

arlake228 commented Nov 3, 2023

A couple things:

  • On the UI for EL9 the tab with the automatic updates toggle and NTP settings is intentionally no longer shown. We are moving away from touch non-perfsonar system level files from the UI. Sounds like you maybe some-how dug it up, but that page is not supported on EL9 and the UI by default intentionally does not show it.
  • The script you mention /usr/lib/perfsonar/scripts/system_environment/testpoint/enable_auto_updates tries to detect the package manager and updates accordingly. It checks for yum-cron and if that doesn't exist it falls back to /etc/dnf/automatic.conf. That script runs the first time you install the RPMs and appears to be working fine on my EL9 system. For reference, that script lives here in git and should match what is on your system: https://github.com/perfsonar/toolkit/blob/master/toolkit/perfsonar-toolkit/scripts/system_environment/testpoint/enable_auto_updates

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Ready
Development

No branches or pull requests

2 participants