Open alexp-openai opened 2 weeks ago
I'm running a quota update command from the cli, like this:
az quota update --scope "/subscriptions/37537258-29ed-4742-87d2-e909358c01fc/providers/Microsoft.Compute/locations/southcentralus" --resource-name "standardDCSv2Family" --limit-object value=7 --resource-type dedicated
And I'm getting an error message "Operation returned an invalid status 'Request Header Fields Too Large'".
I tried running it with --debug flag, and all of the HTTP headers look normal-size. The authorization header is hidden, so maybe it is too long.
Other az commands, like az quota list, work fine.
az quota update
Operation returned an invalid status 'Request Header Fields Too Large'
msal.telemetry: Generate or reuse correlation_id: 900fd643-0e28-4aab-8bf0-98a66d55f1e4 cli.azure.cli.core.sdk.policies: Request URL: 'https://management.azure.com/subscriptions/37537258-29ed-4742-87d2-e909358c01fc/providers/Microsoft.Compute/locations/southcentralus/providers/Microsoft.Quota/quotas/standardDv3Family?api-version=2023-02-01' cli.azure.cli.core.sdk.policies: Request method: 'PATCH' cli.azure.cli.core.sdk.policies: Request headers: cli.azure.cli.core.sdk.policies: 'Content-Type': 'application/json' cli.azure.cli.core.sdk.policies: 'Accept': 'application/json' cli.azure.cli.core.sdk.policies: 'Content-Length': '141' cli.azure.cli.core.sdk.policies: 'x-ms-client-request-id': 'd2e43064-2ccd-11ef-8d01-9ab805ee86ed' cli.azure.cli.core.sdk.policies: 'CommandName': 'quota update' cli.azure.cli.core.sdk.policies: 'ParameterSetName': '--scope --resource-name --limit-object --resource-type --debug' cli.azure.cli.core.sdk.policies: 'User-Agent': 'AZURECLI/2.61.0 (HOMEBREW) azsdk-python-core/1.28.0 Python/3.11.9 (macOS-14.5-x86_64-i386-64bit)' cli.azure.cli.core.sdk.policies: 'Authorization': '*****' cli.azure.cli.core.sdk.policies: Request body: cli.azure.cli.core.sdk.policies: {"properties": {"limit": {"limitObjectType": "LimitValue", "value": 0}, "name": {"value": "standardDv3Family"}, "resourceType": "dedicated"}} urllib3.connectionpool: Starting new HTTPS connection (1): management.azure.com:443 urllib3.connectionpool: https://management.azure.com:443 "PATCH /subscriptions/37537258-29ed-4742-87d2-e909358c01fc/providers/Microsoft.Compute/locations/southcentralus/providers/Microsoft.Quota/quotas/standardDv3Family?api-version=2023-02-01 HTTP/1.1" 431 0 cli.azure.cli.core.sdk.policies: Response status: 431 cli.azure.cli.core.sdk.policies: Response headers: cli.azure.cli.core.sdk.policies: 'Cache-Control': 'no-cache' cli.azure.cli.core.sdk.policies: 'Pragma': 'no-cache' cli.azure.cli.core.sdk.policies: 'Expires': '-1' cli.azure.cli.core.sdk.policies: 'x-ms-ratelimit-remaining-subscription-resource-requests': '23' cli.azure.cli.core.sdk.policies: 'x-ms-request-id': '4db521fc-6d1b-4d59-a509-4425bf93dc08' cli.azure.cli.core.sdk.policies: 'x-ms-correlation-request-id': '4db521fc-6d1b-4d59-a509-4425bf93dc08' cli.azure.cli.core.sdk.policies: 'x-ms-routing-request-id': 'WESTUS:20240617T172001Z:4db521fc-6d1b-4d59-a509-4425bf93dc08' cli.azure.cli.core.sdk.policies: 'Strict-Transport-Security': 'max-age=31536000; includeSubDomains' cli.azure.cli.core.sdk.policies: 'X-Content-Type-Options': 'nosniff' cli.azure.cli.core.sdk.policies: 'X-Cache': 'CONFIG_NOCACHE' cli.azure.cli.core.sdk.policies: 'X-MSEdge-Ref': 'Ref A: F692E25BCBA946C98D4F7EA29C8C7749 Ref B: SJC211051204045 Ref C: 2024-06-17T17:20:01Z' cli.azure.cli.core.sdk.policies: 'Date': 'Mon, 17 Jun 2024 17:20:01 GMT' cli.azure.cli.core.sdk.policies: 'Content-Length': '0'
the command should work without error
azure-cli 2.61.0 core 2.61.0 telemetry 1.1.0 Extensions: quota 1.0.0 Dependencies: msal 1.28.0 azure-mgmt-resource 23.1.1 Python location '/usr/local/Cellar/azure-cli/2.61.0/libexec/bin/python' Extensions directory '/Users/xxx/.azure/cliextensions' Python (Darwin) 3.11.9 (main, Apr 2 2024, 08:25:04) [Clang 15.0.0 (clang-1500.3.9.4)]
No response
Thank you for opening this issue, we will look into it.
Describe the bug
I'm running a quota update command from the cli, like this:
And I'm getting an error message "Operation returned an invalid status 'Request Header Fields Too Large'".
I tried running it with --debug flag, and all of the HTTP headers look normal-size. The authorization header is hidden, so maybe it is too long.
Other az commands, like az quota list, work fine.
Related command
az quota update
Errors
Operation returned an invalid status 'Request Header Fields Too Large'
Issue script & Debug output
Expected behavior
the command should work without error
Environment Summary
Additional context
No response