Bug ID 2365137: Cron job and systemd unit failures occur due to SELinux confd_cli denials

Last Modified: Oct 19, 2026

Affected Product(s):
F5OS F5OS-A, F5OS-C(all modules)

Known Affected Versions:
F5OS v2.0.0, F5OS v2.0.0-HR1, F5OS v2.0.0-HR2, F5OS v2.0.0-HR3, F5OS-A 1.8.4, F5OS-A 1.8.4-HR1, F5OS-A 1.8.4-HR2, F5OS-A 1.8.4-HR3

Opened: Jun 29, 2026

Severity: 3-Major

Symptoms

Scheduled cron jobs that access the ConfD control port fail silently. This also happens to systemd units that access the ConfD control port.

Impact

Any cron-driven or systemd unit workflow that invokes the ConfD via 'f5sh/confd_cli/f5_confd_cli' stops working silently except for connection failures in the job's own output.

Conditions

A scheduled job (cron / system_cronjob_t domain) or systemd unit that connects to the ConfD control port (TCP/4565). For example, anything that invokes one of the following: - /usr/bin/f5sh - confd_cli - f5_confd_cli.

Workaround

Use the "ssh root@localhost f5sh" command instead of f5sh. Note: This requires the usage of another level of quotes. Instead of using the following command: f5sh "config; system database config-backup name otters.xml proceed yes" Use the following command: ssh -o 'BatchMode yes' -o 'LogLevel error' root@localhost f5sh "'config; system database config-backup name otters.xml proceed yes'"

Fix Information

None

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips