[bare metal][tinkerbell] multiple connected NICs cause cluster failure
jacobweinstock opened this issue · 3 comments
What happened:
If multiple NICs are cabled and the first NIC that comes up in HookOS with an IP address is not the NIC specified in the hardware csv it will cause the cluster to fail. This is because we write static network configs and the way in which we determine which network interface to get DHCP info from is only determined based on the first interface that is found up and running with IP info. See this function here:
What you expected to happen:
We should make sure the MAC address is the expected one. This can be done by reading /proc/cmdline as it has the mac address in the hw_addr= arg.
How to reproduce it (as minimally and precisely as possible):
Anything else we need to know?:
Environment:
- EKS Anywhere Release:
- EKS Distro Release:
Hi all - may I know if there is any update on this bug?
closed by #2577
But my fundamental question is why even have a STATIC_NETPLAN. Can I not just use the contents of write netplan to assume all interfaces as Dhcp and make the respective interface as primary... Is that not a valid template config