-
Bug
-
Resolution: Cannot Reproduce
-
Critical
-
None
-
4.11.z
-
None
-
Quality / Stability / Reliability
-
False
-
-
None
-
None
-
No
-
None
-
None
-
Rejected
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Node picked up the wrong IP address and hostname after reboot
First, when the pods tried to start on the nodes their cluster reported that the IP address that is used for the pod on the node (CLusterSDN) in this case 10.7.96.0/19, there were not enough IP addresses. While checking the number of pods there were only 211 pods out of a max 250 on that specific node, so there should have been plenty of free IPs to allocate for the Pods.
We decided to drain and rebooted the compute-14 node. After the reboot, the node picked up the wrong IP address from the same network where the nodes are located. But the hostname was that of an egress IP. I rebooted the same node one more time and then it picked up a different hostname from the same network belonging to another egress host/IP.
For example, the correct IP of the compute-14 is 10.32.20.27
the latest incorrect hostname it got is omnichannels-metrics-egress which belongs to egress IP 10.32.21.183
https://attachments.access.redhat.com/hydra/rest/cases/03465064/attachments/fbfa05de-b420-44c1-9b4c-7d4a47fdde59?usePresignedUrl=true
https://attachments.access.redhat.com/hydra/rest/cases/03465064/attachments/93fa3346-a6ca-4ae2-b5f8-f1b1290c9366?usePresignedUrl=true