Skip to content

Linux OS options for Service Fabric VM OS are incorrect #30381

@wilsncc

Description

@wilsncc

Describe the bug

Azure CLI does not allow deployment of a valid Linux Service Fabric cluster. This is because the only available version via Azure CLI is 16.04 which does not appear to be valid any more.

From the portal, we can see that only Ubuntu Server versions 18.04, 20.04 and 20.04 'Gen2' are available:

Image

Yet Azure CLI only knows of 16.04, which is seemingly not available via the portal:

Image

Related command

az sf cluster create -g some-name-rg -c somecluster -l westeurope --cluster-size 1 --vm-os UbuntuServer2004 --vm-password 'Password#1234' --certificate-output-folder MyCertificates --certificate-subject-name somecluster

Errors

az sf cluster create: 'UbuntuServer2004' is not a valid value for '--vm-os'. Allowed values: WindowsServer2012R2Datacenter, WindowsServer2016Datacenter, WindowsServer2016DatacenterwithContainers, UbuntuServer1604, WindowsServer1709, WindowsServer1709withContainers, WindowsServer1803withContainers, WindowsServer1809withContainers, WindowsServer2019Datacenter, WindowsServer2019DatacenterwithContainers.

Issue script & Debug output

Not necessary, the dictionary simply lacks the correct entries.

Expected behavior

Cluster can be created with valid Ubuntu OS versions, as visible in Azure Portal, including with the Ubuntu Server 20.04 version and also Ubuntu Server 20.04 'Gen2'.

Environment Summary

azure-cli                         2.67.0

core                              2.67.0
telemetry                          1.1.0

Extensions:
resource-graph                     2.1.0

Dependencies:
msal                              1.31.0
azure-mgmt-resource               23.1.1

Python location '/opt/homebrew/Cellar/azure-cli/2.67.0/libexec/bin/python'
Extensions directory '/Users/rosswilson/.azure/cliextensions'

Python (Darwin) 3.12.7 (main, Oct  1 2024, 02:05:46) [Clang 15.0.0 (clang-1500.3.9.4)]

Legal docs and information: aka.ms/AzureCliLegal


Your CLI is up-to-date.

Additional context

Almost certainly due to Microsoft's abandonment of Service Fabric (at least in public). I suspect it's just a case of adding the missing entries to the dictionary, trouble is I'm not sure what the correct value is for the 'Gen2' case.

My employer's sandbox policies don't allow some of the SF cluster resources to deploy and find out myself, and I don't have the Azure credit to try outside of work. Otherwise would raise a PR myself.

Metadata

Metadata

Assignees

Labels

Auto-AssignAuto assign by botService AttentionThis issue is responsible by Azure service team.Service Fabricaz sfbugThis issue requires a change to an existing behavior in the product in order to be resolved.customer-reportedIssues that are reported by GitHub users external to the Azure organization.

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions