Last Modified: Apr 28, 2025
Affected Product(s):
F5OS F5OS
Known Affected Versions:
F5OS-A 1.1.1
Opened: Aug 16, 2022 Severity: 3-Major
When hostname is changed on the appliance, it can result in creation of an extra/faulty K3S node in the K3S cluster with new hostname. Due to this, Tenant deployment will have issues.
K3S cluster will be down. The host will be unable to deploy a tenant.
Intermittently when hostname is changed, followed by a K3S/system restart.
Check if the OMD is Active/running state with "systemctl status appliance_orchestration_manager_container.service". Delete the extra/faulty node with "kubectl delete node <node_name>". Restart k3s service. "systemctl restart k3s.service".
None