-
Bug
-
Resolution: Done-Errata
-
Critical
-
4.14
-
Important
-
No
-
1
-
Metal Platform 242, Metal Platform 243
-
2
-
Approved
-
False
-
-
-
Bug Fix
-
Done
-
-
9/20: considering this green for 4.14 - 4.15 PR merged, and pre-merge test for 4.14
Description of problem:
metal3-baremetal-operator-7ccb58f44b-xlnnd pod failed to start on the SNO baremetal dualstack cluster: Events: Type Reason Age From Message ---- ------ ---- ---- ------- Normal Scheduled 34m default-scheduler Successfully assigned openshift-machine-api/metal3-baremetal-operator-7ccb58f44b-xlnnd to sno.ecoresno.lab.eng.tlv2.redha t.com Warning FailedScheduling 34m default-scheduler 0/1 nodes are available: 1 node(s) didn't have free ports for the requested pod ports. preemption: 0/1 nodes are availabl e: 1 node(s) didn't have free ports for the requested pod ports.. Warning FailedCreatePodSandBox 34m kubelet Failed to create pod sandbox: rpc error: code = Unknown desc = failed to add hostport mapping for sandbox k8s_metal3-baremetal-operator-7ccb58f44b-xlnnd_openshift-machine-api_5f6d8c69-a508-47f3-a6b1-7701b9d3617e_0(c4a8b353e3ec105d2bff2eb1670b82a0f226ac1088b739a256deb9dfae6ebe54): cannot open hostport 60000 for pod k8s _metal3-baremetal-operator-7ccb58f44b-xlnnd_openshift-machine-api_5f6d8c69-a508-47f3-a6b1-7701b9d3617e_0_: listen tcp4 :60000: bind: address already in use Warning FailedCreatePodSandBox 34m kubelet Failed to create pod sandbox: rpc error: code = Unknown desc = failed to add hostport mapping for sandbox k8s_metal3-bare metal-operator-7ccb58f44b-xlnnd_openshift-machine-api_5f6d8c69-a508-47f3-a6b1-7701b9d3617e_0(9e6960899533109b02fbb569c53d7deffd1ac8185cef3d8677254f9ccf9387ff): cannot open hostport 60000 for pod k8s _metal3-baremetal-operator-7ccb58f44b-xlnnd_openshift-machine-api_5f6d8c69-a508-47f3-a6b1-7701b9d3617e_0_: listen tcp4 :60000: bind: address already in use
Version-Release number of selected component (if applicable):
4.14.0-rc.0
How reproducible:
so far once
Steps to Reproduce:
1. Deploy disconnected baremetal SNO node with dualstack networking with agent-based installer 2. 3.
Actual results:
metal3-baremetal-operator pod fails to start
Expected results:
metal3-baremetal-operator pod is running
Additional info:
Checking the pots on node showed it was `kube-apiserver` process bound to the port: tcp ESTAB 0 0 [::1]:60000 [::1]:2379 users:(("kube-apiserver",pid=43687,fd=455)) After rebooting the node all pods started as expected
- blocks
-
OCPBUGS-19545 kube-apiserver bound to port 60000 prevented metal3-baremetal-operator from starting
- Closed
- is cloned by
-
OCPBUGS-19545 kube-apiserver bound to port 60000 prevented metal3-baremetal-operator from starting
- Closed
- links to
-
RHEA-2023:7198 rpm