-
Bug
-
Resolution: Done
-
Normal
-
6.16.0, 6.17.0, 6.18.0
-
1
-
False
-
Moderate
-
Satellite Endeavour Sprint 1
-
sat-endeavour
-
None
-
None
-
None
-
None
-
Yes
Description of problem:
On default installation of Satellite, notifications cleanup (as triggered via cron) fails with error
[2025-05-25 06:00:28] Failed to clean notification: wrong number of arguments (given 1, expected 0)
Trivial reproducer: run the cronjob manually.
How reproducible:
100%
Is this issue a regression from an earlier version:
regression since 6.15 where the cleanup worked well
Steps to Reproduce:
1. /usr/sbin/foreman-rake notifications:clean
Actual behavior:
Starting expired notifications clean up... Failed to clean notification: wrong number of arguments (given 1, expected 0)
Expected behavior:
Like in 6.15:
Starting expired notifications clean up... Finished, cleaned 1 notifications
Business Impact / Additional info:
Both `/usr/share/foreman/lib/tasks/notifications_cleaner.rake` and `/usr/share/foreman/app/services/ui_notifications/clean_expired.rb` are the same on 6.15 and 6.16, the missing argument must be somewhere else..?