Last Modified: May 29, 2024
Affected Product(s):
F5OS Velos
Known Affected Versions:
F5OS-C 1.5.1
Fixed In:
F5OS-C 1.6.0
Opened: Apr 26, 2023 Severity: 3-Major
After blades are added to the Openshift cluster, Multus is installed on the blades via an ansible-playbook. If the blade/blades are rebooted during the playbook run, it is possible that the playbook run could hang, possibly for several hours. During this time, the blade will not be available in the Openshift cluster.
Blade will not be available in the Openshift cluster and will not be able to run tenants.
Adding a new blade, or re-adding an existing blade to the Openshift cluster, and the blade is rebooted during the install of Multus.
If the blades are rebooted during the Multus install and they do not finishing joining the cluster after reboot, the active CC can fail over, which will cause the blade to be added to the cluster again.
Orchestration manager has been updated to run the Multus playbook with a hard timeout, after which it will be retried.