Bug 1726754

Summary:	[docs] When bootstrapping a 4.1 cluster in a VMWare environment the cluster fails to come up
Product:	OpenShift Container Platform	Reporter:	Carsten Lichy-Bittendorf <clichybi>
Component:	Networking	Assignee:	Jason Boxman <jboxman>
Status:	CLOSED DUPLICATE	QA Contact:	zhaozhanqi <zzhao>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	4.1.z	CC:	aos-bugs, bbennett, dmoessne, mstaeble, nagrawal
Target Milestone:	---
Target Release:	4.2.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:
Clones:	1730103 (view as bug list)		Environment:
Last Closed:	2019-08-29 13:42:48 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1730103

Comment 3 Matthew Staebler 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?

Comment 4 Casey Callendrello 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.

Comment 5 Jason Boxman 2019-08-07 17:08:07 UTC

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!

Comment 6 daniel 2019-08-08 03:07:12 UTC

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  ...) " ?

Comment 9 Jason Boxman 2019-08-28 01:14:42 UTC

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.

Comment 10 Neelesh Agrawal 2019-08-29 13:42:48 UTC


*** This bug has been marked as a duplicate of bug 1730103 ***