Description of problem: 4.3 upi/vsphere installation failed due to the bootstrap node ip is not configured as expected. Checked that the bootstrap node was still used the ip offered by dhcp, but not the one configued in ignition file. on bootstrap node: bash-4.4# ifconfig ens192 ens192: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500 inet 139.178.76.56 netmask 255.255.255.192 broadcast 139.178.76.63 inet6 fe80::250:56ff:fe8b:f2ad prefixlen 64 scopeid 0x20<link> ether 00:50:56:8b:f2:ad txqueuelen 1000 (Ethernet) RX packets 53851 bytes 286164221 (272.9 MiB) RX errors 0 dropped 5 overruns 0 frame 0 TX packets 7651 bytes 623958 (609.3 KiB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 the bootstrap ignition file: {"ignition":{"config":{"append":[{"source":"https://s3.us-east-2.amazonaws.com/openshift-qe-upi/vsphere-bootstrap_2019-10-16-23-08-21.ign","verification":{}}]},"timeouts":{},"version":"2.1.0"},"networkd":{},"passwd":{},"storage":{"files":[{"filesystem":"root","group":{},"path":"/etc/hostname","user":{},"contents":{"source":"data:text/plain;charset=utf-8;base64,Ym9vdHN0cmFwLTA=","verification":{}},"mode":420},{"filesystem":"root","group":{},"path":"/etc/sysconfig/network-scripts/ifcfg-ens192","user":{},"contents":{"source":"data:text/plain;charset=utf-8;base64,VFlQRT1FdGhlcm5ldApCT09UUFJPVE89bm9uZQpOQU1FPWVuczE5MgpERVZJQ0U9ZW5zMTkyCk9OQk9PVD15ZXMKSVBBRERSPTEzOS4xNzguNzYuNgpQUkVGSVg9MjYKR0FURVdBWT0xMzkuMTc4Ljc2LjEKRE9NQUlOPWpsaXUtNDN2LnFlLmRldmNsdXN0ZXIub3BlbnNoaWZ0LmNvbQpETlMxPTguOC44LjgK","verification":{}},"mode":420}]},"systemd":{"units":[{"contents":"[Unit]\nConditionFirstBoot=yes\n[Service]\nType=idle\nExecStart=/sbin/reboot\n[Install]\nWantedBy=multi-user.target\n","enabled":true,"name":"restart.service"}]}} decode the ifconfig-ens192: # echo VFlQRT1FdGhlcm5ldApCT09UUFJPVE89bm9uZQpOQU1FPWVuczE5MgpERVZJQ0U9ZW5zMTkyCk9OQk9PVD15ZXMKSVBBRERSPTEzOS4xNzguNzYuNgpQUkVGSVg9MjYKR0FURVdBWT0xMzkuMTc4Ljc2LjEKRE9NQUlOPWpsaXUtNDN2LnFlLmRldmNsdXN0ZXIub3BlbnNoaWZ0LmNvbQpETlMxPTguOC44LjgK|base64 -d TYPE=Ethernet BOOTPROTO=none NAME=ens192 DEVICE=ens192 ONBOOT=yes IPADDR=139.178.76.6 PREFIX=26 GATEWAY=139.178.76.1 DOMAIN=jliu-43v.qe.devcluster.openshift.com DNS1=8.8.8.8 Version-Release number of selected component (if applicable): rhcos-43.80.20191014.2 How reproducible: always Steps to Reproduce: 1. 2. 3. Actual results: ifcfg-ens192 in bootstrap ignition was not applied Expected results: ifcfg-ens192 should be set as expected Additional info: If use 42 boot image rhcos-42.80.20191002.0, it works well. refer to https://bugzilla.redhat.com/show_bug.cgi?id=1736875
might be a duplicate of /related to https://bugzilla.redhat.com/show_bug.cgi?id=1762509
The workaround mentioned above "If use 42 boot image rhcos-42.80.20191002.0, it works well" doesn't work on payload 4.3.0-0.nightly-2019-11-02-092336. Kubelet service on master failed to get started due to: Nov 06 08:05:04 control-plane-0 hyperkube[5385]: F1106 08:05:04.648977 5385 server.go:206] unrecognized feature gate: LegacyNodeRoleBehavior Nov 06 08:05:04 control-plane-0 systemd[1]: kubelet.service: Main process exited, code=exited, status=255/n/a Nov 06 08:05:04 control-plane-0 systemd[1]: kubelet.service: Failed with result 'exit-code'. Nov 06 08:05:04 control-plane-0 systemd[1]: Failed to start Kubernetes Kubelet. Mark this bug as a 4.3 testblocker on vsphere install
Should be fixed as of https://github.com/openshift/installer/pull/2633
The latest rhcos-43.81.201911081536.0 works well now.
Verified on rhcos-43.81.201911081536.0
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, 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/RHBA-2020:0062