-
Bug
-
Resolution: Done-Errata
-
Critical
-
4.14
-
None
-
Moderate
-
No
-
1
-
Metal Platform 240, Metal Platform 241
-
2
-
Approved
-
False
-
Description of problem:
When testing AWS on-prem BM expansion, the BMO is not able to reach the IRONIC_ENDPOINT
Version-Release number of selected component (if applicable):
4.14.0-0.nightly-2023-08-10-021647
How reproducible:
100%
Steps to Reproduce:
1. Install IPI AWS 3-node-compact cluster 2. Deploy BMO via YAML 3. Connect AWS against external on-prem env via VPN (out of scope) 4. Create BMH using "preprovisioningNetworkDataName" to push static IP and routes.
Actual results:
BMO is not able to reach the Ironic endpoint with the following error:
~~~
2023-08-10T16:09:22.216778289Z {"level":"info","ts":"2023-08-10T16:09:22Z","logger":"provisioner.ironic","msg":"error caught while checking endpoint","host":"openshift-machine-api~openshift-qe-065","endpoint":"https://metal3-state.openshift-machine-api.svc.cluster.local:6385/v1/","error":"Get \"https://metal3-state.openshift-machine-api.svc.cluster.local:6385/v1\": dial tcp 172.30.19.119:6385: i/o timeout"}
~~~
Expected results:
Standard deploy
Additional info:
Must-gather provided separatedly
