+++ This bug was initially created as a clone of Bug #2084539 +++ 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?
Verified the PR in https://prow.ci.openshift.org/view/gs/origin-ci-test/pr-logs/pull/openshift_release/28476/rehearse-28476-periodic-ci-openshift-verification-tests-master-installer-rehearse-installer-rehearse-azure/1524986168070901760, it works.
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 (OpenShift Container Platform 4.10.15 bug fix 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/RHBA-2022:2258