Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

VNET integrated CloudShell is not available in germanywestcentral region #366

Open
attilaersek opened this issue Nov 22, 2023 · 2 comments
Assignees
Labels
bug Something isn't working Priority 2

Comments

@attilaersek
Copy link

Couldn't create a vnet integrated cloudshell in the germanywestcentral secondary region. I had to use the az rest method as there's an issue with the portal and the storage selection dropdown is disabled, so there's a chance that the request body is not perfect.

To Reproduce

cloudshell.json request example:

{
    "properties": {
      "preferredOsType": "Linux",
      "preferredLocation": "westeurope",
      "storageProfile": {
        "storageAccountResourceId": "/subscriptions/xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx/resourcegroups/resource-group-xxx/providers/Microsoft.Storage/storageAccounts/storageaccountxxx",
        "fileShareName": "cloudshell",
        "diskSizeInGB": 5
      },
      "terminalSettings": {
        "fontSize": "Medium",
        "fontStyle": "Monospace"
      },
      "preferredShellType": "bash",
      "vnetSettings": {
        "networkProfileResourceId": "/subscriptions/xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx/resourceGroups/resource-group-xxx/providers/Microsoft.Network/networkProfiles/networkprofile-xxx",
        "relayNamespaceResourceId": "/subscriptions/xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx/resourceGroups/resource-group-xxx/providers/Microsoft.Relay/namespaces/relay-xxx",
        "isolatedStorageProfile": {
          "storageAccountResourceId": "/subscriptions/xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx/resourcegroups/resource-group-xxx/providers/Microsoft.Storage/storageAccounts/storageaccountxxx",
          "fileShareName": "cloudshell",
          "diskSizeInGB": 5
        },
        "location": "gernamywestcentral"
      },
      "networkType": "Isolated",
      "sessionType": "Mounted",
      "userSubscription": "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx"
    }
}
az rest --method put --url https://management.azure.com/providers/Microsoft.Portal/userSettings/cloudconsole?api-version=2023-02-01-preview --body @cloudshell.json

Observed Behavior

The request returns with an error:

Bad Request({
  "error": {
    "code": "InvalidLocation",
    "message": "The location 'gernamywestcentral' is invalid."
  }
})

Expected behavior

The cloudshell is created.

Is this specific to Cloud Shell?

Yes.

Interface information

not relevant.

Additional context

Add any other context about the problem here.

@attilaersek attilaersek added bug Something isn't working Triage-needed Triage needed by Cloud Shell team labels Nov 22, 2023
@tovstcn
Copy link

tovstcn commented Nov 27, 2023

We are experiencing the same issue for germanywestcentral, different regions are working fine.

Addition: I stumbled upon this Issue -> #222 - It looks like secondary regions are currently not supported for vnet isolation (as mentioned here -> https://learn.microsoft.com/en-us/samples/azure/azure-quickstart-templates/cloud-shell-vnet-storage

Does this issue still deserve the "bug" flag?

@attilaersek
Copy link
Author

attilaersek commented Nov 30, 2023

This restriction is not mentioned in the feature documentation and the portal also allows you to select secondary regions. (Though currently the portal fails to create vnet integrated cloudshell for any region.).
The problem seems to be a simple request validation issue, but could be more.
Despite this, the issue can be relabeled to feature request or closed as duplicate, but the lack of this feature limits the usability of cloudshell.

@mbifeld mbifeld self-assigned this Apr 9, 2024
@mbifeld mbifeld added Priority 2 and removed Triage-needed Triage needed by Cloud Shell team labels Apr 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working Priority 2
Projects
None yet
Development

No branches or pull requests

3 participants