-
Bug
-
Resolution: Unresolved
-
Major
-
4.20
-
Quality / Stability / Reliability
-
False
-
-
1
-
Important
-
None
-
None
-
Approved
-
Metal Platform 276, Metal Platform 277
-
2
-
In Progress
-
Release Note Not Required
-
None
-
None
-
None
-
None
-
None
This is a clone of issue OCPBUGS-60455. The following is the description of the original issue:
—
Sometime between 4.20.0-0.nightly-2025-07-31-063120 and 4.20.0-0.ci-2025-08-12-172211 Ironic started using port 8089, i.e.
[jcaamano@sdn-08 ~]$ oc --insecure-skip-tls-verify --request-timeout=20s rsh -n openshift-ovn-kubernetes -c ovnkube-controller ovnkube-node-75q26 ss -apn | grep 8089
tcp LISTEN 0 5 [::1]:8089 [::]:* users:(("ironic",pid=13669,fd=6))
At the same time k-nmstate operator running as host-networking pod uses 8089. As a result, k-nmstate cannot any more start because 8089 is already used by Ironic.
As per gentlemen's agreement, k-nmstate was there first so Ironic should move to use another port.
At the same time, we should document (https://github.com/openshift/enhancements/blob/master/dev-guide/host-port-registry.md) the new port Ironic is going to use (k-nmstate will document theirs too).
- clones
-
OCPBUGS-60455 Port 8089 used by Ironic and k-nmstate
-
- Verified
-
- is blocked by
-
OCPBUGS-60455 Port 8089 used by Ironic and k-nmstate
-
- Verified
-
- links to