Bug ID 2225253: Kubervirt is stuck in unhealthy state due sw-mgmt port differences on controllers

Last Modified: Mar 05, 2026

Affected Product(s):
F5OS None(all modules)

Known Affected Versions:
F5OS-C 1.8.0, F5OS-C 1.8.1, F5OS-C 1.8.2

Opened: Feb 18, 2026

Severity: 3-Major

Symptoms

Kubervirt is stuck in unhealthy state due to port mismatch on different CCs. If cluster was brought up using one CC assigned port, it is stuck in unhealthy state if the same port is used to pull containers from the other CC.

Impact

Kubervirt is stuck in unhealthy state.

Conditions

Sw-mgmt port assignment to the service version must be different on differnt CCs. When the CCs were baremetal installed , import of ISO failed on one CC due to signature verification failure. Because ISO got imported on one CC and not the other this led to port mismatches.

Workaround

As the port mismatch in this case is due to signature verification failure. Please check the ISO import status after baremetal and in case of failure copy the ISO from healthy CC to the other. OR Perform a HA failover in this case the CC with unimported state becomes stand by and syncs it self with active and will get the same port assignment.

Fix Information

None

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips