-
Bug
-
Resolution: Unresolved
-
Undefined
-
None
-
4.21, 4.22
Description of problem:
This bug tracks the renaming issue in https://github.com/openshift/installer/pull/10162. Generally, existing vnet is required for private cluster creation, which is described in openshift installation document[1]. But for edge scenario if private cluster is not created in byo vnet, vnet will be created by installer. In this case, ssh rule is still created, and no inboundNAT is created, installer seems likely to fail when destroying bootstrap, because of https://github.com/openshift/installer/blob/main/pkg/infrastructure/azure/azure.go#L630-L664 [1] https://docs.redhat.com/en/documentation/openshift_container_platform/4.20/html-single/installing_on_azure/index#private-clusters-default_installing-azure-private
Version-Release number of selected component (if applicable):
4.21
How reproducible:
Always
Steps to Reproduce:
1. Create private cluster without byo vnet settings
2.
3.
Actual results:
installation failed
Expected results:
installation succeeded
Additional info:
- blocks
-
OCPBUGS-73878 Azure: install failed during destroying bootstrap if private cluster is not created in byo vnet
-
- POST
-
- is cloned by
-
OCPBUGS-73878 Azure: install failed during destroying bootstrap if private cluster is not created in byo vnet
-
- POST
-
- links to