-
Bug
-
Resolution: Unresolved
-
Normal
-
None
-
6.16.z, 6.17.z, 6.18.0
-
False
-
sat-endeavour
-
None
-
None
-
None
-
None
Description of problem:
When running the foreman_tasks:cleanup rake task in Red Hat Satellite 6.18, repeated WARN messages are logged:
W, [2025-08-28T14:21:32.042081 #11329] WARN -- : Scoped order is ignored, it's forced to be batch order. W, [2025-08-28T14:21:32.724949 #11329] WARN -- : Scoped order is ignored, it's forced to be batch order.
How reproducible:
100%
Is this issue a regression from an earlier version:
Upgraded from 6.17 to 618
Steps to Reproduce:
1. Log in to a Satellite 6.18 server.
2. Run any foreman-rake task:
For ex.
# foreman-rake katello:correct_repositories COMMIT=true --trace ** Invoke katello:correct_repositories (first_time) ** Invoke environment (first_time) ** Execute environment W, [2025-08-28T15:33:16.355238 #14605] WARN -- : Scoped order is ignored, it's forced to be batch order. W, [2025-08-28T15:33:18.114831 #14605] WARN -- : Scoped order is ignored, it's forced to be batch order. W, [2025-08-28T15:33:18.533274 #14605] WARN -- : Scoped order is ignored, it's forced to be batch order. W, [2025-08-28T15:33:18.694908 #14605] WARN -- : Scoped order is ignored, it's forced to be batch order. W, [2025-08-28T15:33:19.201782 #14605] WARN -- : Scoped order is ignored, it's forced to be batch order. W, [2025-08-28T15:33:19.714123 #14605] WARN -- : Scoped order is ignored, it's forced to be batch order. ** Invoke katello:check_ping (first_time) ** Invoke environment ** Invoke dynflow:client (first_time) ** Invoke environment ** Execute dynflow:client ** Execute katello:check_ping ** Execute katello:correct_repositories Processing Repository 1/54: Red Hat Satellite Client 6 for RHEL 7 Server RPMs x86_64 (1) Processing Repository 2/54: Red Hat Enterprise Linux 8 for x86_64 - BaseOS RPMs 8 (2) Processing Repository 3/54: Red Hat Enterprise Linux 8 for x86_64 - AppStream RPMs 8 (3) Processing Repository 4/54: Red Hat Satellite Client 6 for RHEL 8 x86_64 RPMs (4) Processing Repository 5/54: Red Hat Enterprise Linux 9 for x86_64 - BaseOS RPMs 9 (5) Processing Repository 6/54: Red Hat Enterprise Linux 9 for x86_64 - AppStream RPMs 9 (6) Processing Repository 7/54: Red Hat Satellite Client 6 for RHEL 9 x86_64 RPMs (7) Processing Repository 8/54: Red Hat Enterprise Linux 7 Server Kickstart x86_64 7.9 (8) Processing Repository 9/54: Red Hat Enterprise Linux 8 for x86_64 - AppStream Kickstart 8.10 (9) Processing Repository 10/54: Red Hat Enterprise Linux 8 for x86_64 - BaseOS Kickstart 8.10 (10) Processing Repository 11/54: Red Hat Enterprise Linux 9 for x86_64 - AppStream Kickstart 9.5 (11) Processing Repository 12/54: Red Hat Enterprise Linux 9 for x86_64 - BaseOS Kickstart 9.5 (12)
Another example:
# foreman-rake foreman_tasks:cleanup TASK_SEARCH='label ~ *' AFTER='3d' TASK_BACKUP=fal se W, [2025-10-02T12:19:56.719561 #394090] WARN -- : Scoped order is ignored, it's forced to be batch order. ......many many lines.... W, [2025-10-02T12:27:27.618363 #394090] WARN -- : Scoped order is ignored, it's forced to be batch order. W, [2025-10-02T12:27:34.286335 #394090] WARN -- : Scoped order is ignored, it's forced to be batch order. W, [2025-10-02T12:27:42.495846 #394090] WARN -- : Scoped order is ignored, it's forced to be batch order. Deleted 52115 tasks matching filter No orphaned task locks found, skipping. About to remove 203408 orphaned task links Deleted 203408 orphaned task links No orphaned execution plans found, skipping. No orphaned job invocations found, skipping.
Actual behavior:
Task runs successfully, but many WARN messages appear:
"Scoped order is ignored, it's forced to be batch order."
Expected behavior:
Foreman-rake should run without WARN spam, or warnings should be suppressed/handled gracefully.
Impact:
Creates confusion for administrators, who may misinterpret these WARN messages as an error in cleanup.
Noisy output makes it harder to verify actual progress.
