Skip to content

Creating a Service Connector via the CLI threw an unexpected error (not clear enough for a user to correct)Β #30296

@benjaminapetersen

Description

@benjaminapetersen

Describe the bug

I was able to create a service connector via the Azure Portal, but I expected this to work. The error was not clear enough for me to know what to do to resolve the issue:

az aks connection create keyvault --connection my_connection_name --resource-group my-rg1 --name aks-cluster-name --target-resource-group my-rg1 --vault my-akv1 --enable-csi --client-type none    
# cli.azure.cli.core.azclierror: (GeneralUserError) Execution failed. Operation returned an invalid status code 'Conflict'
# Code: GeneralUserError

Related command

az aks connection

Errors

# cli.azure.cli.core.azclierror: (GeneralUserError) Execution failed. Operation returned an invalid status code 'Conflict'
# Code: GeneralUserError

Issue script & Debug output

No script needed.

Expected behavior

A clear error that indicates how I can resolve the issue.

Environment Summary

az version
{
"azure-cli": "2.65.0",
"azure-cli-core": "2.65.0",
"azure-cli-telemetry": "1.1.0",
"extensions": {
"interactive": "1.0.0b1",
"scenario-guide": "0.1.1"
}
}

Additional context

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    AKSaz aks/acs/openshiftAuto-AssignAuto assign by botService AttentionThis issue is responsible by Azure service team.bugThis issue requires a change to an existing behavior in the product in order to be resolved.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions