powershell - Azure diagnostics extension ConflictError for empty Staging slot (Azure SDK 2.6) -
i deploying azure cloud service deployment empty staging slot new-azuredeployment in powershell along extension configuration diagnostics created via new-azureservicediagnosticsextensionconfig.
when swap production , call:
get-azureservicediagnosticsextension -servicename "my-service-name-here" -slot production
the "id" property comes "myrole-paasdiagnostics-staging-ext-0". note still says "staging".
now, if try new deployment staging error says:
new-azuredeployment : conflicterror: extension id myrole-paasdiagnostics-staging-ext-0 in use deployment.
this seems broken since there nothing deployed staging @ time. way can deploy new cloud service "staging" diagnostics extension if first delete diagnostics extension "production" remove-azureservicediagnosticsextension.
is bug or thoughts on might doing wrong? didn't see option let me specify alternate id extension.
update
this feels bug me. if do:
get-azureservicediagnosticsextension -servicename "my-service" -slot production
i extension staging id. if following:
remove-azureservicediagnosticsextension -servicename "my-service" -slot production
i (note: extension deployed staging , swapped production):
warning: no existing microsoft.azure.diagnostics.paasdiagnostics extensions enabled on given roles.
if following:
remove-azureservicediagnosticsextension -servicename "my-service" -slot staging
i back:
remove-azureservicediagnosticsextension : deployment not found in service: my-service , slot: staging.
so, appears have 0 means of removing diagnostics extension without first deploying new slot.
turns out reported bug on github azure-powershell project: https://github.com/azure/azure-powershell/issues/193
and looks submitted potential fix too.
Comments
Post a Comment