Azure / Azure/azure-cli

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

Open
#30,296 2 comments 1 reaction 0 assignees View on GitHub
act-observability-squad AKS Auto-Assign bug Service Attention
Dominant language
Python
Stars
4.6k
Forks
3.5k
Avg merge
3d 2h
Merged PRs (30d)
60

Description

### 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:

```bash
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_

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.