Bug 2037813 - Metal Day 1 Networking - networkConfig Field Only Accepts String Format
Summary: Metal Day 1 Networking - networkConfig Field Only Accepts String Format
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Installer
Version: 4.10
Hardware: All
OS: All
medium
medium
Target Milestone: ---
: 4.10.0
Assignee: Andrea Fasano
QA Contact: Yoav Porag
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-01-06 15:47 UTC by Yoav Porag
Modified: 2022-03-10 16:37 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-03-10 16:37:33 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github openshift installer pull 5545 0 None open Bug 2037813: [baremeta] networkConfig field now accepts yaml instead of string value 2022-01-18 14:26:47 UTC
Red Hat Product Errata RHSA-2022:0056 0 None None None 2022-03-10 16:37:45 UTC

Description Yoav Porag 2022-01-06 15:47:06 UTC
What happened?

Currently, when editing install-config.yaml and adding the 'networkConfig' field as part of metal day-1 networking, the networkConfig field will only accept input in string format.

example:
  hosts:
      - name: openshift-master-0
        ...
        networkConfig: |
          interfaces:
          - name: eth0
        ...

This detracts from the advantages of using YAML format and makes for a bad user experience.


What did you expect to happen?

Accepting a yaml format instead of (or as well as) a string would allow for better user experience and error verification.

example:
    hosts:
      - name: openshift-master-0
        ...
        networkConfig: 
          interfaces:
          - name: eth0
        ...

Comment 3 Yoav Porag 2022-01-23 12:11:40 UTC
installation with static ip node succeeded in yaml format.

[kni@provisionhost-0-0 ~]$ vi install-config.yaml 
........
      - name: openshift-master-0-0
        role: master
        bmc:
          address: redfish://192.168.123.1:8000/redfish/v1/Systems/892b423c-1681-455d-9fe0-1e0baa474492
          disableCertificateVerification: True
          username: admin
          password: password
        bootMACAddress: 52:54:00:2a:24:21
        networkConfig:
          routes:
            config:
            - destination: 0.0.0.0/0
              next-hop-address: 192.168.123.1
              next-hop-interface: enp0s4
          dns-resolver:
            config:
              server:
              - 192.168.123.1
          interfaces:
          - name: enp0s4
            type: ethernet
            state: up
            ipv4:
              address:
              - ip: 192.168.123.100
                prefix-length: 24
              enabled: true
        rootDeviceHints:
          deviceName: /dev/sda
........

[kni@provisionhost-0-0 ~]$ oc get nodes
NAME                                              STATUS   ROLES    AGE   VERSION
master-0-0.ocp-edge-cluster-0.qe.lab.redhat.com   Ready    master   39m   v1.23.0+e7c8504
master-0-1                                        Ready    master   42m   v1.23.0+e7c8504
master-0-2                                        Ready    master   42m   v1.23.0+e7c8504
worker-0-0                                        Ready    worker   14m   v1.23.0+e7c8504
worker-0-1                                        Ready    worker   14m   v1.23.0+e7c8504


verified

Comment 6 errata-xmlrpc 2022-03-10 16:37:33 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Moderate: OpenShift Container Platform 4.10.3 security update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2022:0056


Note You need to log in before you can comment on or make changes to this bug.