Dell APEX Cloud Platform: Build failed at step "Wait For OCP Bootstrap Ready"
Summary: APEX Cloud Platform for Red Hat OpenShift build failed at the step of "Wait For OCP Bootstrap Ready"
This article applies to
This article does not apply to
This article is not tied to any specific product.
Not all product versions are identified in this article.
Symptoms
APEX Red Hat Openshift cluster build failed at step 18/36 as below:
Figure1: Build failed at step18/36
From short.term.log, error returned from the OCP cluster build step -- duplicate IP validation:
One Mac address 00:24:38:bf:b7:xx returned, showing it's binding to all the validated IPs.
Figure1: Build failed at step18/36
From short.term.log, error returned from the OCP cluster build step -- duplicate IP validation:
One Mac address 00:24:38:bf:b7:xx returned, showing it's binding to all the validated IPs.
"2024-03-04 16:40:03,841" microservice.mcp-installer-ocp "2024-03-04T16:40:02.972585964Z stderr F 2024-03-04 16:40:02[36m [INFO] <5128>[0m command.go func2() (55): level=warning msg=Collisions detected for host ID 178e700d-dc93-d4c4-083f-a2efe475c240, IP address: 10.0.1.xx Mac addresses: 00:24:38:bf:b7:xx,58:a2:e1:39:18:xy" "2024-03-04 16:50:03,841" microservice.mcp-installer-ocp "2024-03-04T16:50:03.358794718Z stderr F 2024-03-04 16:50:03[36m [INFO] <5128>[0m command.go func2() (55): level=warning msg=Collisions detected for host ID 673de92a-51ad-549c-d5d5-0b81283403e9, IP address: 10.0.1.xy Mac addresses: 00:24:38:bf:b7:xx,58:a2:e1:2d:8b:zx" "2024-03-04 17:05:09,841" microservice.mcp-installer-ocp "2024-03-04T17:05:09.177826344Z stderr F 2024-03-04 17:05:09[36m [INFO] <5128>[0m command.go func2() (55): level=warning msg=Collisions detected for host ID 178e700d-dc93-d4c4-083f-a2efe475c240, IP address: 10.0.0.xx Mac addresses: 00:24:38:bf:b7:xx,58:a2:e1:39:18:xy" "2024-03-04 17:10:04,841" microservice.mcp-installer-ocp "2024-03-04T17:10:04.283117445Z stderr F 2024-03-04 17:10:04[36m [INFO] <5128>[0m command.go func2() (55): level=warning msg=Collisions detected for host ID 178e700d-dc93-d4c4-083f-a2efe475c240, IP address: 10.0.1.xx Mac addresses: 00:24:38:bf:b7:xx,58:a2:e1:39:18:xz" "2024-03-04 17:14:32,841" microservice.mcp-installer-ocp "2024-03-04T17:14:32.05180267Z stderr F 2024-03-04 17:14:32[36m [INFO] <5128>[0m command.go func2() (55): level=error msg=Bootstrap failed to complete: : bootstrap process timed out: context deadline exceeded" "2024-03-04 17:14:32,841" microservice.mcp-installer-ocp "2024-03-04T17:14:32.055900087Z stderr F 2024-03-04 17:14:32[31m [ERROR] <5114>[0m command.go RunCmd() (72): command fail to execute: openshift-install agent wait-for bootstrap-complete --dir manifest --log-level debug"
Cause
Arp proxy used in the customer network
Resolution
Locate the Arp proxy server in the network and disable it at the time of cluster deployment or block the specific Mac from the top switch.
May refer to KB000120449 ( How to configure IP ACL in DELL Networking N-Series Switches) for ACL part or reach out to switch vendor for configuration guide.
Additional Information
The switch-level ACL is intended to block all ARP traffic from the specified MAC address. This will indirectly cause any IP addresses served by that MAC address to become unreachable while the ACL is active. If the Proxy ARP traffic is being generated by the subnet's gateway router be aware that all requests to things outside the subnet (such as DNS/NTP servers) will fail.
Affected Products
APEX Cloud Platform for Red Hat OpenShiftArticle Properties
Article Number: 000222842
Article Type: Solution
Last Modified: 05 مارس 2026
Version: 5
Find answers to your questions from other Dell users
Support Services
Check if your device is covered by Support Services.