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?
That is definitely some deep arcana there. I'll leave it up to our docs writer, Jason Boxman, to decide.
Hi Carsten, Would a user provisioning a cluster on VMware normally generate MAC addresses? Or when creating VMs does VMware automatically provide an ethernet device with a proper MAC address? How common is this issue? Thanks!
Hi Jason, when a user runs the process manually through the VMware UI (clicking) the VM gets the MAC address assigned automagically, however user can change (parts) of it. Haven't played a long time with it, but if I do recall correctly the OUI part is unchangeable and just the last digits can be changed. BUT in enterprise environments it is rarely done manually and automation tools are used, e.g. ansible, where MAC addresses are more configurable which then leads to issues. So I would say this is meanwhile the more common method for deploying and hence relevant. Possibly we can have something in the docs like "If using automation tool for deploying VM, ensure the provided MAC address (range) is matching your VMWare environment assigned pool/range of MAC addresses ...) " ?
I'm tracking the documentation update in the following BZ: https://bugzilla.redhat.com/show_bug.cgi?id=1730103 It may make sense to close this issue.
*** This bug has been marked as a duplicate of bug 1730103 ***