Last Modified: Jul 10, 2026
Affected Product(s):
F5OS F5OS-A, F5OS-C
Known Affected Versions:
F5OS-A 1.8.4
Opened: Jun 26, 2026 Severity: 3-Major
A scheduled cron job that previously worked stops running after upgrading to a version containing the fix for ID1185573 and ID1994869. The job is still listed by "crontab -l" and works when run by hand, but never executes on schedule, with nothing logged.
User-defined scheduled jobs silently fail to run after upgrade unless they're the first entry in the crontab file. Failure is silent: the job is present in "crontab -l", runs correctly when invoked manually, and produces no errors or SELinux denials. System-managed (F5-owned) crontabs are NOT affected.
-- A user-defined crontab (e.g., root's crontab) or an /etc/cron.d file containing more than one schedulable entry. -- The entry that fails to run is any entry after the first in that file.
Place the required job as the FIRST entry in the crontab (or in its own single-entry /etc/cron.d file). This is a positional workaround only and is fragile - adding further entries, or any reordering, will cause later entries to silently stop running again.
None