Connect failed when multiple subscriptions are logged in

[super-kevin]

Hi team,
I can connect to the serial console using Azure CLI with only one subscription logged in:

az serial-console connect --name aaa --resource-group bbb

After I log in the second subscription, I use --subscription option to connect to the serial console in the first subscription:

az serial-console connect --subscription "b20abce3-xxxx-xxxx-xxxx-9fa4dbe5xxxx" --name aaa --resource-group bbb

However, it failed with An unexpected error occurred:

For more information on the Azure Serial Console, see <https://aka.ms/serialconsolelinux>.
Connecting to console of VM   □ □ ■
An unexpected error occurred. Could not establish connection to VM or VMSS. Check network connection and press "Enter" to try again...

How to debug this?

Thanks in advance for your time and help!

Here are the subscriptions on my host:

az account list
[
  {
    "cloudName": "AzureCloud",
...
    "id": "b20abce3-xxxx-xxxx-xxxx-9fa4dbe5xxxx",
    "isDefault": true,
    "managedByTenants": [],
    "name": "Visual Studio Professional Subscription",
    "state": "Enabled",
...
  },
  {
    "cloudName": "AzureCloud",
...
    "id": "d9abef03-xxxx-xxxx-xxxx-873426f7xxxx",
    "isDefault": false,
    "managedByTenants": [],
    "name": "Azure subscription 1",
    "state": "Enabled",
...
  }
]

[super-kevin]

Here is the --debug output:

cli.azure.cli.core.sdk.policies: Request URL: 'https://management.azure.com/subscriptions/b20abce3-xxxx-xxxx-xxxx-9fa4dbe5xxxx/resourcegroups/bbb/providers/Microsoft.Compute/virtualMachines/aaa/providers/Microsoft.SerialConsole/serialPorts/0/connect?api-version=2018-05-01'
cli.azure.cli.core.sdk.policies: Request method: 'POST'
cli.azure.cli.core.sdk.policies: Request headers:
cli.azure.cli.core.sdk.policies:     'Accept': 'application/json'
cli.azure.cli.core.sdk.policies:     'Accept-Language': 'en'
cli.azure.cli.core.sdk.policies:     'Content-Type': 'application/json'
cli.azure.cli.core.sdk.policies:     'x-ms-client-request-id': 'dda765a7-968a-11ef-bca3-54bf64a781e7'
cli.azure.cli.core.sdk.policies:     'CommandName': 'serial-console connect'
cli.azure.cli.core.sdk.policies:     'ParameterSetName': '--debug --subscription --name --resource-group'
cli.azure.cli.core.sdk.policies:     'User-Agent': 'AZURECLI/2.64.0 (MSI) azsdk-python-core/1.28.0 Python/3.11.8 (Windows-10-10.0.20348-SP0)'
cli.azure.cli.core.sdk.policies:     'Authorization': '*****'
cli.azure.cli.core.sdk.policies: Request body:
cli.azure.cli.core.sdk.policies: This request has no body
urllib3.connectionpool: Starting new HTTPS connection (1): management.azure.com:443
Connecting to console of VM   ■ □ □urllib3.connectionpool: https://management.azure.com:443 "POST /subscriptions/b20abce3-xxxx-xxxx-xxxx-9fa4dbe5xxxx/resourcegroups/bbb/providers/Microsoft.Compute/virtualMachines/aaa/providers/Microsoft.SerialConsole/serialPorts/0/connect?api-version=2018-05-01 HTTP/1.1" 500 78
cli.azure.cli.core.sdk.policies: Response status: 500
cli.azure.cli.core.sdk.policies: Response headers:
cli.azure.cli.core.sdk.policies:     'Cache-Control': 'no-cache'
cli.azure.cli.core.sdk.policies:     'Pragma': 'no-cache'
cli.azure.cli.core.sdk.policies:     'Content-Length': '78'
cli.azure.cli.core.sdk.policies:     'Content-Type': 'application/json'
cli.azure.cli.core.sdk.policies:     'Expires': '-1'
cli.azure.cli.core.sdk.policies:     'x-ms-ratelimit-remaining-subscription-writes': '199'
cli.azure.cli.core.sdk.policies:     'X-FRAME-OPTIONS': 'deny'
cli.azure.cli.core.sdk.policies:     'X-Content-Type-Options': 'nosniff'
cli.azure.cli.core.sdk.policies:     'x-ms-correlation-request-id': '2c66204e-a405-4f6e-9ef6-32f9ede93f23'
cli.azure.cli.core.sdk.policies:     'x-ms-request-id': '43590e60-2d51-429f-9e25-d1c0c8a5287f'
cli.azure.cli.core.sdk.policies:     'Strict-Transport-Security': 'max-age=31536000; includeSubDomains'
cli.azure.cli.core.sdk.policies:     'x-ms-failure-cause': 'service'
cli.azure.cli.core.sdk.policies:     'x-ms-ratelimit-remaining-subscription-global-writes': '2999'
cli.azure.cli.core.sdk.policies:     'x-ms-routing-request-id': 'WESTUS:20241030T064748Z:2c66204e-a405-4f6e-9ef6-32f9ede93f23'
cli.azure.cli.core.sdk.policies:     'X-Cache': 'CONFIG_NOCACHE'
cli.azure.cli.core.sdk.policies:     'X-MSEdge-Ref': 'Ref A: 4CA3D01B0EBE45CFB2BFBE9B684DB083 Ref B: SEL221051801039 Ref C: 2024-10-30T06:47:47Z'
cli.azure.cli.core.sdk.policies:     'Date': 'Wed, 30 Oct 2024 06:47:48 GMT'
cli.azure.cli.core.sdk.policies: Response content:
cli.azure.cli.core.sdk.policies: {
  "code": "InternalOperationError",
  "message": "Internal Server Error."
 }

[mbifeld]

Hi @super-kevin , thanks for reporting this issue. I was able to successfully use the serial-console connect command on a subscription that wasn't actively set. I do notice that the debug output time was when there was an active outage in Serial Console. Can you try running it again? Thanks