Last Modified: Jun 19, 2025
Affected Product(s):
F5OS Velos
Fixed In:
F5OS-C 1.8.1
Opened: Feb 12, 2025 Severity: 3-Major
If there are other issues on the chassis that cause the ansible playbooks to run slowly during Kubernetes cluster install, the playbook cannot be retried correctly if it reaches timeout.
The Kubernetes cluster install may fail repeatedly because it will not correctly recognize the timeout, and raise the amount of time it will wait.
This can occur, if there are other issues on the chassis that cause the ansible playbooks to run slowly, such as DNS or remote auth issues when a Kubernetes cluster rebuild is executed.
Mitigation is resolve the issue(s) causing the playbooks to run slowly. This may involving removing bad DNS servers or remote auth servers that may be causing the slow down.
The orchestration-manager code has been updated to correctly recognize the timeout error, and handle it correctly.