-
Bug
-
Resolution: Not a Bug
-
Critical
-
None
-
premerge
-
Moderate
-
No
-
Sprint 245
-
1
-
False
-
Description of problem:
When set invalid subnetName and vnetName in config.image crd for azure cluster, still set successfully.
Version-Release number of selected component (if applicable):
4.15.0-0.ci.test-2023-11-16-012054-ci-ln-wbdfj3b-latest
How reproducible:
always
Steps to Reproduce:
1. Launch a azure cluster 2. set invaild value for subnetName and vnetName in config.image/cluster azure: accountName: imageregistrywewang2n4qg cloudName: AzurePublicCloud container: wewang-azurepr-g6spt-image-registry-tspenpcekgvbalwigbjjywiusl networkAccess: internal: privateEndpointName: imageregistrywewangmdrnq subnetName: azurepr-g6spt-master-subnet vnetName: zurepr-g6spt-vnet
Actual results:
It set successfully
Expected results:
should give error info for the user
Additional info: