{AKS} Fix the test failure of network isolated cluster feature

bingosummer commented 2 weeks ago

This checklist is used to make sure that common guidelines for a pull request are followed.

Related command

az aks create --resource-group={resource_group} --name={name} --bootstrap-artifact-source Cache --bootstrap-container-registry-resource-id {acr_id} --outbound-type=none/block

General Guidelines

[ ] Have you run azdev style <YOUR_EXT> locally? (pip install azdev required)
[ ] Have you run python scripts/ci/test_index.py -q locally? (pip install wheel==0.30.0 required)
[ ] My extension version conforms to the Extension version schema

For new extensions:

[ ] My extension description/summary conforms to the Extension Summary Guidelines.

About Extension Publish

There is a pipeline to automatically build, upload and publish extension wheels.
Once your pull request is merged into main branch, a new pull request will be created to update src/index.json automatically.
You only need to update the version information in file setup.py and historical information in file HISTORY.rst in your PR but do not modify src/index.json.

azure-client-tools-bot-prd[bot] commented 2 weeks ago

️✔️Azure CLI Extensions Breaking Change Test

>

️✔️Non Breaking Changes

> > >

azure-client-tools-bot-prd[bot] commented 2 weeks ago

Hi @bingosummer, Please write the description of changes which can be perceived by customers into HISTORY.rst. If you want to release a new extension version, please update the version in setup.py as well.

yonzhan commented 2 weeks ago

Thank you for your contribution! We will review the pull request and get back to you soon.

github-actions[bot] commented 2 weeks ago

For more info about extension versioning, please refer to Extension version schema

FumingZhang commented 2 weeks ago

Queued live test to validate the change.

test_aks_network_isolated_cluster

Case failed with the following error

E                   azure.cli.core.azclierror.BadRequestError: (InvalidNetworkIsolatedClusterConfiguration) When outbound type is none or block, the cluster must be private cluster or enables apiserver vnet integration
E                   Code: InvalidNetworkIsolatedClusterConfiguration
E                   Message: When outbound type is none or block, the cluster must be private cluster or enables apiserver vnet integration

FumingZhang commented 2 weeks ago

Queued live test to validate the change.

test_aks_network_isolated_cluster

Case failed with the following error

E                   azure.cli.core.azclierror.BadRequestError: (InvalidNetworkIsolatedClusterConfiguration) When outbound type is none or block, the cluster must be private cluster or enables apiserver vnet integration
E                   Code: InvalidNetworkIsolatedClusterConfiguration
E                   Message: When outbound type is none or block, the cluster must be private cluster or enables apiserver vnet integration

Requeued live test

bingosummer commented 2 weeks ago

Requeued live test, test passed!

test_aks_network_isolated_cluster

FumingZhang commented 2 weeks ago

/azp run

azure-pipelines[bot] commented 2 weeks ago

Azure Pipelines successfully started running 2 pipeline(s).

FumingZhang commented 2 weeks ago

/azp run

azure-pipelines[bot] commented 2 weeks ago

Azure Pipelines successfully started running 2 pipeline(s).

FumingZhang commented 2 weeks ago

/azp run

azure-pipelines[bot] commented 2 weeks ago

Azure Pipelines successfully started running 2 pipeline(s).

Azure / azure-cli-extensions