-
Bug
-
Resolution: Not a Bug
-
Major
-
None
-
4.13
-
Critical
-
No
-
2
-
Metal Platform 233, Metal Platform 234
-
2
-
Rejected
-
False
-
Description of problem:
Trying to scale up baremetal server which locate in pek2 lab as remote worker to existing IPI baremetal cluster which located rdu2. The remote worker boot failed.
Version-Release number of selected component (if applicable):
4.13
How reproducible:
always
Steps to Reproduce:
1. Setup IPI baremetal cluster with servers in rdu2 lab 2. Scale up another lab server as remote worker with yaml file $ cat remote_14.yaml --- apiVersion: v1 kind: Secret metadata: name: openshift-14-bmc-secret namespace: openshift-machine-api type: Opaque data: username: cm9vdAo= password: Y2FsdmluCg==--- apiVersion: metal3.io/v1alpha1 kind: BareMetalHost metadata: name: bj14 namespace: openshift-machine-api spec: online: true bmc: address: redfish://10.73.116.63/redfish/v1/Systems/System.Embedded.1 disableCertificateVerification: True credentialsName: openshift-14-bmc-secret bootMACAddress: e4:43:4b:5b:6c:28 rootDeviceHints: hctl: 1:0:0:0 3. oc apply -f remote_14.yaml 4. $ oc get Baremetalhost -A NAMESPACE NAME STATE CONSUMER ONLINE ERROR AGE openshift-machine-api bj14 inspecting true 30m
Actual results:
server cannot be boot
Expected results:
Additional info: