-
Bug
-
Resolution: Not a Bug
-
Major
-
None
-
4.16
-
None
-
Quality / Stability / Reliability
-
False
-
-
None
-
Moderate
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Description of problem:
When trying to scale up a MachineSets with multiple interfaces configured with static IPs it does not work. When inspecting the VM afterburn the data is present, however is not associated to any interface and both address get assigned to one interface: ------------------------------------------- govc vm.info -json /DC/vm/Folder/test-cluster1-mdcsn-worker-static-jf76h | grep -A 1 afterburn "key": "guestinfo.afterburn.initrd.network-kargs", "value": "ip=192.xxx.x.1:::255.xxx.xxx.0:::none nameserver=10.xx.xxx.1 ip=10.xx.xxx.233::10.xx.2xxx.254:255.xxx.xxx.0:::none nameserver=10.xx.xxx.1 " -------------------------------------------
Steps to Reproduce:
1. Follow documentation [https://docs.openshift.com/container-platform/4.16/post_installation_configuration/node-tasks.html#nodes-vsphere-machine-set-scaling-static-ip_post-install-node-tasks] 2. Use configure two interfaces
Actual results:
Depending on the interface order the configuration get associated to the different interfaces, seems like both address get assigned to one interface: [core@test-cluster1-mdcsn-worker-static-jf76h ~]$ ip -br a lo UNKNOWN 127.0.0.1/8 ::1/128 ens192 UP ens224 UP 192.xxx.x.1/24 10.xx.xxx.233/23
Expected results:
The IPs can land on the configured NIC/networkName and create successfully the node.
- links to