-
Bug
-
Resolution: Unresolved
-
Normal
-
None
-
4.18.z
-
Quality / Stability / Reliability
-
False
-
-
None
-
Important
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Description of problem:
As per discussion and agent-gather in slack: https://redhat-internal.slack.com/archives/C02SPBZ4GPR/p1747658384927159
ABI Baremetal rendezvous host does not join nor logs detect anything clear when requests from the cluster nodes to the VIP ingress are blocked by firewall. The logs does not show any actual input of why it is not joining, it is showing bootstrap as completed correctly. It would be great to add a validation of such or logs to proof that there is issue in that communication.
Version-Release number of selected component (if applicable):
4.18.z
How reproducible:
Install ABI in a situation where requests from the cluster nodes to the VIP ingress are blocked by firewall. No logs are being showed.
Actual results:
Logs are not helpful, rendezvous host is not rebooting nor joining the cluster, bootstrap is marked as completed. Troubleshooting is messy.
Expected results:
Having logs pointing such issue or a validation test of such traffic during installation. Bug is because this should still allow the cluster node to join probably as then it should be handled to workers.
Additional info:
Logs can be found in slack or in case 04140953.
