+++ This bug was initially created as a clone of Bug #1726754 +++
Description of problem:
when trying to install OCP 4.1 on VMware the process reproducible hangs with:
- pod sdn-controller log shows: "subnets.go:42] Node IP is not set for node" for all nodes.
- all pod sdn show: subnets.go:159] Could not find an allocated subnet for node: <node>, Waiting...
- sdn pod logs
Please advice on what additional data is required.
--- Additional comment from Carsten Lichy-Bittendorf on 2019-07-03 16:04 UTC ---
--- Additional comment from Carsten Lichy-Bittendorf on 2019-07-03 16:05 UTC ---
--- Additional comment from Matthew Staebler on 2019-07-08 16:40:12 UTC ---
This was resolved on the customer side by using MAC addresses with VMWare OIDs. Is there anything more that needs to be done for this bug? Should we add guidance on MAC addresses to the vSphere install docs?
--- Additional comment from Casey Callendrello on 2019-07-15 20:04:57 UTC ---
That is definitely some deep arcana there. I'll leave it up to our docs writer, Jason Boxman, to decide.
"VMWare requires that the MAC addresses be in the range of 00:50:56:00:00:00 to 00:50:56:3F:FF:FF."
I've created a PR for this bug.
*** Bug 1726754 has been marked as a duplicate of this bug. ***