-
Bug
-
Resolution: Unresolved
-
Major
-
None
-
4.13, 4.12, 4.11, 4.14
-
Important
-
No
-
False
-
-
Release Note Not Required
-
In Progress
Description of problem:
"networkd" section should not be defined in merge-bootstrap.ign
#ENV:
- OCP4.14
- vSphere infra, installation in restricted network with UPI
#ISSUE
- bootstrap node shows the message when accessing console terminal of the vm.
~~~
Ignition: warning at $.networkd: Unused key networkd
~~~
The message appears in the ignition verification process because the "networkd" section is not supported in the ignition configuration since Ignition version 3.0
According to the official documentation[1],
"merge-bootstrap.ign" file is used for boostrap node in the vSphere environment.
The file is Ignition version 3.2
[1]https://docs.openshift.com/container-platform/4.14/installing/installing_vsphere/installing-restricted-networks-vsphere.html#installation-vsphere-machines_installing-restricted-networks-vsphere
~~~
Save the following secondary Ignition config file for your bootstrap node to your computer as <installation_directory>/merge-bootstrap.ign:
{
"ignition": {
"config": {
"merge": [
{
"source": "<bootstrap_ignition_config_url>",
"verification": {}
}
]
},
"timeouts": {},
"version": "3.2.0"
},
"networkd": {}, // This is not a supported configuration in the Ignition 3.2 spec[2], and should be deleted.
"passwd": {},
"storage": {},
"systemd": {}
}
~~~
The guided ignition config file should be fixed in the documentation.
"networkd": {} line should be deleted from merge-bootstrap.ign example in the documentation.
Because Ignition 3.2 version does not support the "networkd" section.
Version-Release number of selected component (if applicable):
OCP4.14, OCP4.13, OCP4.12, OCP4.11
How reproducible:
Install openshift cluster in vSphere infra by following the documentation. https://docs.openshift.com/container-platform/4.14/installing/installing_vsphere/installing-restricted-networks-vsphere.html#installation-vsphere-machines_installing-restricted-networks-vsphere
Steps to Reproduce:
1. Install the cluster following the procedures in the documentation[1].
2. Boot the bootstrap node and access vm console terminal
3. The warning message appears
"Ignition: warning at $.networkd: Unused key networkd"
Actual results:
The warning message appears in vm console "Ignition: warning at $.networkd: Unused key networkd" ~~~ Red Hat Enterprise Linux CoreOS 414.92.202310170514-0 (Plow) 4.14 SSH host key: SHA256: XXXXXXXXXXX (ED25519) SSH host key: XXXXXXXXXXXX(ECDSA) SSH host key: XXXXXXXXX (RSA) ens192:XXX.XXX.XXX.XXX Ignition: ran on 2024/01/24 09:11:34 UTC (at least 3 boots ago) Ignition: user-provided config was applied Ignition: warning at $.networkd: Unused key networkd ==> This warning message appears bootstrap login: [ 33.099687] Warning: Deprecated Driver is detected: nft_compat will not be maintained in a future major rele ase and may be ~~~
Expected results:
No ignition warning message is displayed.
Additional info:
[2]Networkd section is not supported in Ignition version 3.2 - https://coreos.github.io/ignition/configuration-v3_2/ [3]Networkd section is removed since Ignition 3.0 - https://coreos.github.io/ignition/migrating-configs/#networkd-section-is-removed
