-
Bug
-
Resolution: Done-Errata
-
Major
-
4.11
-
Moderate
-
None
-
Rejected
-
False
-
Description of problem:
When we exapnd the baremetal IP cluster with static IP, no information is logged if nmstate output is "--- {}\n" and the customized image generates without the static network configuration.
Version-Release number of selected component (if applicable):
4.11
How reproducible:
100%
Steps to Reproduce:
1. Exapand baremetal ipi cluster node with the below invalid nmstate data. --- apiVersion: v1 kind: Secret metadata: name: openshift-worker-0-network-config-secret type: Opaque stringData: nmstate: | foo: bar: baz --- apiVersion: v1 kind: Secret metadata: name: openshift-worker-0-bmc-secret namespace: openshift-machine-api type: Opaque data: username: YWRtaW4K password: cGFzc3dvcmQK --- apiVersion: metal3.io/v1alpha1 kind: BareMetalHost metadata: name: openshift-worker-0 namespace: openshift-machine-api spec: online: True bootMACAddress: 52:54:00:11:22:b4 bmc: address: ipmi://192.168.123.1:6233 credentialsName: openshift-worker-0-bmc-secret disableCertificateVerification: True username: admin password: password rootDeviceHints: deviceName: "/dev/sda" preprovisioningNetworkDataName: openshift-worker-0-network-config-secret 2. Check if an IP is configured with the node 3.
Actual results:
No static network configuration in the metal3 customized image.
Expected results:
Information should be logged and the metal3 customized image should not be generated.
Additional info:
https://github.com/openshift/image-customization-controller/pull/72
- is duplicated by
-
OCPBUGS-11537 BMH with static network configuration gets stuck in inspecting state when network configuration secret is invalid without any pointers to an invalid user configuration
- Closed
- links to
-
RHEA-2023:5006 rpm