CaioCavalcanti
commented
4 years ago Just had the same problem here, swap operation failed at some point (I found the error below on the activity logs) and the identity of the staging slot was lost. Did you manage to fix this problem?
[...]
"operationId": "b984304d-66a7-42ee-b8a4-be68c87fbf0c",
"operationName": {
"value": "Microsoft.Web/sites/slots/slotsswap/action",
"localizedValue": "Swap Web App Slots"
},
[...]
"properties": {
"statusCode": "InternalServerError",
"serviceRequestId": null,
"statusMessage": "{\"Code\":\"InternalServerError\",\"Message\":null,\"Target\":null,\"Details\":[{\"Message\":null},{\"Code\":\"InternalServerError\"},{\"ErrorEntity\":{\"Code\":\"InternalServerError\",\"Message\":null}}],\"Innererror\":null}"
},
By "Idendity" I mean this feature:
My app got run through our release pipeline, including a slot swap. The slot swap was not successful and eventually timed out after about 10 minutes. This problem is that the Identity of the production slot got switched off. This means, the app could not connect to Key Vault anymore, so no secrets could be retrieved and the app was therefore essentially unusable. What I would expect is that the Identity is unchanged after a failed slot swap and stays on so that the production slot keeps running.
Investigative information
Repro steps
Provide the steps required to reproduce the problem:
I could repro the problem with my specific app:
*The reason of the swap timeout is unknown to me. I could repro it when running my CI/CD pipeline, as well as doing the swap manually via the portal. Usually a slot swap takes less than 2 minutes. I have swapped the slots of this app and similar apps many times before without any problems.
Expected behavior
Identity is still on after a failed slot swap.
Actual behavior
Identity got switched off after the failed slot swap
Known workarounds
Switch on Identity manually after the failed swap attempt. The id is the same as before.
Related information
Excerpt from the build log