search

MicrosoftDocs / azure-docs

Open source documentation of Microsoft Azure
https://docs.microsoft.com/azure
Creative Commons Attribution 4.0 International
10.22k stars 21.37k forks source link

The build / package environment must also have SF .Net SDK at CU2 or higher #39014

Closed MedAnd closed 4 years ago

MedAnd commented 5 years ago

Please add to the documentation clarification that the build / package environment must also have the SF .Net SDK at CU2 or higher, and not just the target cluster run-time being at CU2.

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

jakaruna-MSFT commented 5 years ago

@MedAnd Thanks for the feedback! We are currently investigating and will update you shortly.

jakaruna-MSFT commented 5 years ago

@athinanthny Please validate this request. I can edit the doc after your confirmation.

jakaruna-MSFT commented 5 years ago

@MedAnd I am following up internally with the content author to get his confirmation to edit the doc.

athinanthny commented 5 years ago

@jakaruna-MSFT We publish SDK version# in our public blog, docs and release notes doc per release. Below are links

https://docs.microsoft.com/en-us/azure/service-fabric/service-fabric-versions#supported-versions

https://techcommunity.microsoft.com/t5/Azure-Service-Fabric/Azure-Service-Fabric-6-5-Second-Refresh-Release/ba-p/800523

https://github.com/Azure/service-fabric/blob/master/release_notes/Service_Fabric_ReleaseNotes_65CU2.pdf

MedAnd commented 5 years ago

Please allow me to clarify above. I followed the guidance in the docs only to find out that it’s mandatory for my build server to also have SF .Net SDK at CU2 installed otherwise the package step silently removes any refs to Managed Identity from the xml as it does not pass schema validation. Given the failure is silent I then attempted to deploy via ARM, a process feedback loop that can take 20mins+. The attempt failed and resulted in a support issue. I thought this knowledge would help other customers as the documentation skips over vital information.

jakaruna-MSFT commented 5 years ago

Thanks @MedAnd When i went through the doc, In SDK the Cu* versioning is not followed. So if service fabric runtime version is 6.5.658.9590(CU2), Then I think the sdk should be equal to or greater than 658. (3.4.658)
Are you looking for adding this info to the doc

These version numbers are taken from this release doc

MedAnd commented 4 years ago

The guide omitted the fact the build/package server must have the correct SF .Net SDK installed. The guide only highlights that the SF runtime on the target cluster must be at CU2.... but one cannot deploy unless they’ve built & packaged their application correctly which can only happen with the correct SF .Net SDK version. Hope that makes sense?

jakaruna-MSFT commented 4 years ago

@athinanthny Can you please update the requested details to the Document?

mimckitt commented 4 years ago

I went ahead and added that info to the note at the top of the page.

once the PR merges the changes will go live after a few hours.