This post has been republished via RSS; it originally appeared at: MSDN Blogs.
On 2/6, a security update to the Ubuntu xenial rssh package was made available via public Ubuntu package sources. The updated version (2.3.4-4+deb8u1build0.16.04.1) introduced a fault in Service Fabric's ImageBuilder process. This process is used when provisioning applications and the cluster runtime in Service Fabric. Ubuntu based Service Fabric nodes will be unable to do core management operations unless the dependent package is downgraded to the previous version (2.3.4-4).
This will impact any new Azure based Service Fabric clusters, any new nodes added to an existing cluster, or any nodes which have the upgraded package version (this is applicable if you have manually requested a reimage of any VM(s) in your scale sets). Existing clusters that have not been scaled up or do not have nodes that have been reimaged, should not be affected. If your cluster is currently not affected, we recommend that you avoid reimaging or scaling your cluster till we roll out a fix for this issue.
Here is a script to help mitigate the issue that needs to be applied as a Custom Script Extension to your ARM (Azure Resource Manager) template, followed by an upgrade to apply the change to your cluster. Instructions for doing this are noted below. You will need to do this for existing as well as new clusters until we work to fix the issue on our end. Please watch this space for future updates on this.
Instructions for applying the fix:
Update your ARM template
In your ARM template that represents the latest configuration of your deployment, edit the extensions section to include a ‘CustomScriptExtension’ that contains the script we are providing to help mitigate the issue. Right below the definition of the ‘ServiceFabricVMExtension,’ add the following JSON snippet:
{
"name": " [concat(variables('vmNodeType0Name'),'_rssh_2_4_4-4-fix')]",
"properties": {
"publisher": "Microsoft.Azure.Extensions",
"settings": {
"fileUris": [
"https://gist.githubusercontent.com/mhatreabhay/695a90331c29dcb83ef7d439b394ad5d/raw/77e3f877c2c0cdd160dbbb618b83fd21ee50edd4/rssh_2_4_4-4_sf.py"
]
},
"typeHandlerVersion": "2.0","autoUpgradeMinorVersion": true,
"protectedSettings": {
"commandToExecute": "./rssh_2_4_4-4_sf.py"
},
"type": "CustomScript"
}
}
Update your cluster deployment
Once your ARM template is ready, deploy the template using the corresponding PowerShell or Azure CLI command -
Azure CLI:
az group deployment create -g MyResourceGroup --template-file azuredeploy.json --parameters azuredeploy.parameters.json
PowerShell:
New-AzureRmResourceGroupDeployment -ResourceGroupName MyResourceGroup -TemplateFile azuredeploy.json -TemplateParameterFile azuredeploy.parameters.json
Please reach out to us if you need specific assistance with this issue through Azure Portal Help. In addition, here are your general support options for Service Fabric: https://docs.microsoft.com/en-us/azure/service-fabric/service-fabric-support#report-production-issues-or-request-paid-support-for-azure. We will keep you appraised of any updates on this matter through the blog. Thank you!