Details
-
Bug
-
Resolution: Not a Bug
-
Undefined
-
None
-
4.11.0
-
None
-
Moderate
-
False
-
Description
Description of problem:
When expanding a bare metal cluster, an nmstate configuration is supplied as directed in step 4 https://docs.openshift.com/container-platform/4.11/installing/installing_bare_metal_ipi/ipi-install-expanding-the-cluster.html#preparing-the-bare-metal-node_ipi-install-expanding The goal of the setting is to disable a 1GbE interface via nmstate. the interface receives both dns and dhcp which are not desired in the cluster. [kni@perf166 dev-scripts]$ cat perf158.yml --- apiVersion: v1 kind: Secret metadata: name: perf158-network-config-secret type: Opaque stringData: nmstate: | interfaces: - name: eno3 type: ethernet state: down ipv4: enabled: false ipv6: enabled: false --- apiVersion: v1 kind: Secret metadata: name: lblyth-perf158-bmc-secret type: Opaque data: username: cm9vdA== password: MTAweWFyZC0= --- apiVersion: metal3.io/v1alpha1 kind: BareMetalHost metadata: name: perf158.logan.perf.lab.metal3.io spec: online: true bootMACAddress: 1c:34:da:77:35:68 bmc: address: idrac://perf158-drac.perf.lab.eng.bos.redhat.com credentialsName: lblyth-perf158-bmc-secret preprovisioningNetworkDataName: perf158-network-config-secret
Version-Release number of selected component (if applicable):
How reproducible:
100%
Steps to Reproduce:
1.setup a cluster via the dev-scripts project 2.expand the bare metal cluster using the steps provided in the documentation linked above 3. when the system is showing as available in the oc get bmh output. look at the console of the machine via iDrac/IPMI. It shows the device configured via dhcp.
Actual results:
the interface is up and showing the dhcp configuration
Expected results:
the interface is disabled, and does not accept a dhcp/dns
Additional info: