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

Bug 2084539

Summary:	update azure arm templates to support customer provided vnet
Product:	OpenShift Container Platform	Reporter:	Johnny Liu <jialiu>
Component:	Installer	Assignee:	Johnny Liu <jialiu>
Installer sub component:	openshift-installer	QA Contact:	Johnny Liu <jialiu>
Status:	CLOSED ERRATA	Docs Contact:
Severity:	medium
Priority:	medium	CC:	padillon
Version:	4.10
Target Milestone:	---
Target Release:	4.11.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	No Doc Update
Doc Text:	This was a change to UPI templates for CI. We don't need to document this.	Story Points:	---
Clone Of:
Clones:	2084547 (view as bug list)		Environment:
Last Closed:	2022-08-10 11:11:30 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:	2084547

Description Johnny Liu 2022-05-12 11:58:16 UTC

Per the azure upi arm templates in https://github.com/openshift/installer/tree/master/upi/azure, it assumes the vnet is always created from 01_vnet.json with the same basename from infra id. 

Actually for some special cases, vnet maybe provisioned in advanced, UPI process will skip vnet creation step, e.g: https://github.com/openshift/release/pull/27977, create other resources in the provided customer vnet. 

So we need to update the existing templates to introduce a new optional parameter - vnetBaseName for that.

Version:

$ openshift-install version
<your output here>

Platform:

Azure

Please specify:
* UPI (semi-manual installation on customized infrastructure)

What happened?

Comment 1 Johnny Liu 2022-05-12 12:15:46 UTC

This is verified in https://github.com/openshift/release/pull/28476, it works.

Comment 3 errata-xmlrpc 2022-08-10 11:11:30 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Important: OpenShift Container Platform 4.11.0 bug fix and security update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2022:5069