az-cli v 2.34.1: az webapp deployment slot create -- errors when configuration-source has a path-mapping to storage #21965
Comments
|
route to CXP team |
|
@apapajohn Thank you for reaching out to us. We are looking into it. |
|
@apapajohn I managed to get it to work with az version 2.34.1 with the similar environment as yours. Can you please share share the debug trace for the issue, of course after sanitizing sensitive information from the log. |
|
c:\dev\abcdefgzzffffxxxxxxx\xxxxxxx\xxxxxxx-frontend>az webapp deployment slot create --name abcdefg-myservice --resource-group abcdefgzz-xxxxxxxxxxx_-rgp-q1-abcdefgzzffff-ase --configuration-source abcdefg-myservice --slot temp34debug --debug During handling of the above exception, another exception occurred: Traceback (most recent call last): cli.azure.cli.core.azclierror: Required parameter AccessKey is missing. |
Please see above debug log. |
|
@apapajohn Thank you for the logs, i am able to reproduce the issue after using --configuration-source parameter. I am investigating further will keep you posted |
|
Maybe I closed this by accident. Reopening. |
|
@apapajohn no worries, we are still investigating the issue, will update as soon as we find a cause/mitigation. |
|
Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @antcp, @AzureAppServiceCLI. Issue DetailsDescribe the bug We upgraded az-cli from 2.33.1 to 2.34.1 and it broke our app service deployment pipeline, at the point where it creates a deployment slot. It seems to be because the az-cli command is attempting to copy the azure-blob mapping information over to the slot. It is erroring with the message "Required parameter AccessKey is missing.", even though there is no available AccessKey parameter for the az webapp deployment slot create command. As a result, the slot gets created, but it is incomplete. Not all the configuration gets copied over from the configuration source. To Reproduce
Expected behavior A deployment slot gets created and all the config info gets copied over from the app service. az-cli 2.34.1 on DOS or LINUX (happens on both) I ran the failing command with the --debugging flag and I can see where it is failing:
|
|
@StrawnSC Please help us with an update. |
|
I haven't started work on a fix for this yet. I'll see if I can get a fix for this in the May 2022 release |
Describe the bug
We upgraded az-cli from 2.33.1 to 2.34.1 and it broke our app service deployment pipeline, at the point where it creates a deployment slot. It seems to be because the az-cli command is attempting to copy the azure-blob mapping information over to the slot. It is erroring with the message "Required parameter AccessKey is missing.", even though there is no available AccessKey parameter for the az webapp deployment slot create command.
As a result, the slot gets created, but it is incomplete. Not all the configuration gets copied over from the configuration source.
To Reproduce
Expected behavior
A deployment slot gets created and all the config info gets copied over from the app service.
Environment summary
az-cli 2.34.1 on DOS or LINUX (happens on both)
Additional context
I ran the failing command with the --debugging flag and I can see where it is failing:
cli.azure.cli.core.sdk.policies: {"properties": {"numberOfWorkers": 1, "defaultDocuments": [] ....,xxxxxprivateinfoxxxxxxxxxx ... "http20Enabled": true, "minTlsVersion": "1.2", "scmMinTlsVersion": "1.0", "ftpsState": "Disabled", "preWarmedInstanceCount": 0, "functionAppScaleLimit": 0, "functionsRuntimeScaleMonitoringEnabled": false, "minimumElasticInstanceCount": 0, "azureStorageAccounts": {"lucene-index": {"type": "AzureBlob", "accountName": "xxxprivateinfo", "shareName": "xxxprivateinfo", "mountPath": "/tmp/lucene"}}}}
urllib3.connectionpool: Starting new HTTPS connection (1): management.azure.com:443
urllib3.connectionpool: https://management.azure.com:443 "PATCH /subscriptions/xxxprivateinfo/web?api-version=2021-03-01 HTTP/1.1" 400 391
cli.azure.cli.core.sdk.policies: Response status: 400
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: 'Content-Length': '391'
cli.azure.cli.core.sdk.policies: 'Content-Type': 'application/json; charset=utf-8'
cli.azure.cli.core.sdk.policies: 'Expires': '-1'
cli.azure.cli.core.sdk.policies: 'ETag': '"1D849DB703AD940"'
cli.azure.cli.core.sdk.policies: 'Strict-Transport-Security': 'max-age=31536000; includeSubDomains'
cli.azure.cli.core.sdk.policies: 'Server': 'Microsoft-IIS/10.0'
cli.azure.cli.core.sdk.policies: 'X-AspNet-Version': '4.0.30319'
cli.azure.cli.core.sdk.policies: 'X-Powered-By': 'ASP.NET'
cli.azure.cli.core.sdk.policies: 'x-ms-ratelimit-remaining-subscription-writes': '1199'
cli.azure.cli.core.sdk.policies: 'x-ms-request-id': '5ab0772a-3e6a-4532-aadf-272fcb708596'
cli.azure.cli.core.sdk.policies: 'x-ms-correlation-request-id': '5ab0772a-3e6a-4532-aadf-272fcb708596'
cli.azure.cli.core.sdk.policies: 'x-ms-routing-request-id': 'EASTUS:20220406T172627Z:5ab0772a-3e6a-4532-aadf-272fcb708596'
cli.azure.cli.core.sdk.policies: 'X-Content-Type-Options': 'nosniff'
cli.azure.cli.core.sdk.policies: 'Date': 'Wed, 06 Apr 2022 17:26:26 GMT'
cli.azure.cli.core.sdk.policies: Response content:
cli.azure.cli.core.sdk.policies: {"Code":"BadRequest","Message":"Required parameter AccessKey is missing.","Target":null,"Details":[{"Message":"Required parameter AccessKey is missing."},{"Code":"BadRequest"},{"ErrorEntity":{"ExtendedCode":"01010","MessageTemplate":"Required parameter {0} is missing.","Parameters":["AccessKey"],"Code":"BadRequest","Message":"Required parameter AccessKey is missing."}}],"Innererror":null}
cli.azure.cli.core.util: azure.cli.core.util.handle_exception is called with an exception:
cli.azure.cli.core.util: Traceback (most recent call last):
The text was updated successfully, but these errors were encountered: