Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 2051452

Summary: pre-requisites of OCP Installation on vSphere which says multiple OCP clusters cannot reside on the same L2.
Product: OpenShift Container Platform Reporter: bmehra
Component: DocumentationAssignee: Donna DaCosta <ddacosta>
Status: CLOSED DEFERRED QA Contact: zhaozhanqi <zzhao>
Severity: high Docs Contact: Tomas 'Sheldon' Radej <tradej>
Priority: unspecified    
Version: 4.8CC: cherraz, clasohm, ddacosta, jpasztor, moddi, pprinett
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-03-09 01:12:31 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:

Description bmehra 2022-02-07 09:43:19 UTC
Document URL:  
https://docs.openshift.com/container-platform/4.8/installing/installing_vsphere/installing-vsphere-installer-provisioned.html
Section Number and Name: 



Describe the issue: 

pre-requisites of OCP Installation on Bare Metal and vSphere which says multiple OCP clusters cannot reside on the same L2 subnet.

1. When we have multiple cluster on VSphere/BareMetal VRIDs conflicts with other cluster on same broadcast domain.[1]

[1]https://github.com/openshift/installer/blob/master/docs/user/metal/install_ipi.md







Suggestions for improvement: 

Additional information:

Comment 1 Cristina Herraz 2022-03-14 16:31:48 UTC
Reached out to Bobby for clarification on the problem descrption and the vesions the BZ applies to.

Comment 2 Cristina Herraz 2022-03-17 10:26:56 UTC
Created PR --> https://github.com/openshift/openshift-docs/pull/43386

Questions still pending:
- Is this the best place to add this info?
- Is this only applicable to bare metal and vsphere?
- Which versions does this apply to? Created on master for now to start the conversation.

Comment 3 Cristina Herraz 2022-03-22 14:13:39 UTC
Got information from engineering (Ben Nemec) about my questions. 

"This does not apply to baremetal. It's not a problem to install multiple clusters in a subnet on that platform in any supported release. The only ones where this is a concern are vsphere, openstack, and ovirt, and those should also be fixed in 4.11 by openshift/machine-config-operator#3016

Also note that there is a way to safely run multiple clusters on a subnet. The process described in https://access.redhat.com/solutions/6450581 needs to be followed to ensure there are no conflicts.

This does only apply to IPI, so we don't want to mention it in any UPI docs."


Closing the PR and opening one in 4.10, since this is fixed in 4.11 (main).

Comment 4 Cristina Herraz 2022-03-22 14:15:36 UTC
Created new PR --> https://github.com/openshift/openshift-docs/pull/43599

Comment 5 Cristina Herraz 2022-03-25 10:18:44 UTC
@bmehra the new PR is up, please check it out when you can.

I've also requested review from Ben Nemec directly on the PR

Comment 6 Cristina Herraz 2022-04-06 09:47:47 UTC
SME review complete. Requesting QE review -- It's not Amit's team. Asking Xiaoli Tian

Comment 7 Cristina Herraz 2022-04-07 12:54:05 UTC
QE assigned. Requesting Peer review as well, no merging yet.

Comment 8 Cristina Herraz 2022-04-14 15:14:58 UTC
While on my search for QEs, found out there had been a similar PR before for another BZ that was never merged:

https://github.com/openshift/openshift-docs/pull/35316
https://bugzilla.redhat.com/show_bug.cgi?id=1886450


Talked to Donna DaCosta about it, and the SME that was helping her get the content right, Janos Bonic.  There's still a bit of a conundrum about what's needed where: Ben Nemec said this applies to 4.10 and earlier, for Openstack, vSphere, and RHV IPI, but in Donna's PR it seems the fix isn't applicable for 4.10,  and that Openstack is not affected.

Donna's gracefully agreed to keep working on her PR to get this fixed. On my side, I talked to Janos to put him in contact with Ben so that they can discuss and come with a plan for this BZ from the eng point of view.  Janos will be busy for the next 2 weeks on a release but should be available afterwards. 

I suggest my PR to be closed and this BZ marked as duplicate. Will consult with the DPM.

Comment 14 Shiftzilla 2023-03-09 01:12:31 UTC
OpenShift has moved to Jira for its defect tracking! This bug can now be found in the OCPBUGS project in Jira.

https://issues.redhat.com/browse/OCPBUGS-9109