search

microsoft / service-fabric-issues

This repo is for the reporting of issues found with Azure Service Fabric.
168 stars 21 forks source link

Azure Service Fabric deployment issue #1337

Closed dirkslab closed 5 years ago

dirkslab commented 5 years ago

We have the following environments sbx, dev, tst, stg and prd. All Azure ARM resources gets deployed using VSTS CI/CD pipeline. I regularly deploy (running for almost a year). Today Azure Service Fabric Cluster deployment Step started failing. There has been no changes to the SFC ARM template and the last round of deployments in Sept 2018 were all successful. If I redeploy the last successful deployment, I still get this new error. Please see error below from VSTS failed Release.

At least one resource deployment operation failed. Please list deployment operations for details. Please see https://aka.ms/arm-debug for usage details. Details: BadRequest: { "error": { "code": "BadRequest", "message": "On resource 'sfctstpri', extension name 'VMDiagnosticsVmExt_vmNT1Name' cannot be used for more than one extension." } } undefined Task failed while creating or updating the template deployment.

vipul-modi commented 5 years ago

@ChackDan @vaishnavk - can you comment?

srrengar commented 5 years ago

Can you check how many VMSS extensions in your template have the name "VMDiagnosticsVmExt_vmNT1Name" it appears each must have a unique name

dirkslab commented 5 years ago

Can you check how many VMSS extensions in your template have the name "VMDiagnosticsVmExt_vmNT1Name" it appears each must have a unique name

Thanks @srrengar. I have checked and it appears only once in the Template. We have been deploying without an issue for almost a year. I can send you the template if required.

aljo-microsoft commented 5 years ago

@dirkslab

hello, please reach out to me at aljo@microsoft.com if you are still having this issue.

dirkslab commented 5 years ago

@dirkslab

hello, please reach out to me at aljo@microsoft.com if you are still having this issue.

Thanks @aljo-microsoft, I will do a deploy this morning to confirm issue is still there and then reach out to you with feedback.

dirkslab commented 5 years ago

just an fyi update. I wanted to start updating my sf clusters to use managed identity. So could not keep this issue on the backlog anymore. All deployments ran fine, without above mentioned issues. I presume update to sf, windows update or fixed backend issue must have been resolved by Azure. Thanks.

ChackDan commented 5 years ago

Thankyou Dirk.

From: Dirk Slabbert notifications@github.com Sent: Wednesday, April 3, 2019 1:44 AM To: Azure/service-fabric-issues service-fabric-issues@noreply.github.com Cc: Chacko Daniel chackdan@microsoft.com; Assign assign@noreply.github.com Subject: Re: [Azure/service-fabric-issues] Azure Service Fabric deployment issue (#1337)

just an fyi update. I wanted to start updating my sf clusters to use managed identity. So could not keep this issue on the backlog anymore. All deployments ran fine, without above mentioned issues. I presume update to sf, windows update or fixed backend issue must have been resolved by Azure. Thanks.

— You are receiving this because you were assigned. Reply to this email directly, view it on GitHubhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FAzure%2Fservice-fabric-issues%2Fissues%2F1337%23issuecomment-479397196&data=02%7C01%7Cchackdan%40microsoft.com%7C6732c99785e644624a7508d6b8108bc6%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636898778532230231&sdata=A1qwXKvfrHv%2BWPzPp6kKqhePLb3%2BARKzu6ANuHTECvY%3D&reserved=0, or mute the threadhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAKq9pvRWjOv_rtl2pb3cxaU6l7ylJEzXks5vdGnbgaJpZM4YCPZn&data=02%7C01%7Cchackdan%40microsoft.com%7C6732c99785e644624a7508d6b8108bc6%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636898778532240239&sdata=Y4MGumLF4ogr%2Fdab8Daps6hvq7BWJ1CozlScs4lOXH0%3D&reserved=0.