Instructions do not work for default Visual Studio Code online Linux host

[BharathNimmala-MSFT]

az feedback auto-generates most of the information requested below, as of CLI version 2.0.62

Describe the bug
This a escalation from CLI GitHub docs repo
MicrosoftDocs/azure-docs-cli#1649

Appears to be Ubuntu 18.04.1 (output of uname -a is "Linux 4f95409cc772 5.0.0-1023-azure #24~18.04.1-Ubuntu SMP Wed Oct 2 20:23:29 UTC 2019 x86_64 GNU/Linux.") Fails on "lsb_release -cs."

Help needed to understand if there is any ongoing issues which team is aware of , which might affect on what customer is trying to evaluate with Visual studio code online Linux host.

To Reproduce
Customer is following this documentation https://docs.microsoft.com/en-us/cli/azure/install-azure-cli-apt?view=azure-cli-latest#feedback , but getting the following error

Expected behavior
The steps in the docs should work.

Environment summary
Ubuntu 18.04.1

Additional context
Please help evaluate any product related issues or its primarily doc needs to be updated

[fengzhou-msft]

Thanks for reporting the issue. I will investigate.

[fengzhou-msft]

I created a Ubuntu 18.04 vm and uname -a shows
Linux feng-ubuntu-18 5.0.0-1025-azure #27~18.04.1-Ubuntu SMP Mon Nov 11 15:19:19 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

I cannot reproduce the issue. lsb_release -cs gives me bionic as expected.

[alexvy86]

I have a similar issue, lsb_release -cs gives me stretch (Debian?), even though uname -a says Ubuntu, and in fact when selecting the VM for my VSO environment, there were only Ubuntu options. I think I misremembered, I only get options that say "Linux", not specifically Ubuntu... still, why do uname -a and lsb_release -cs don't match?

This environment is in EastUS, in case that's relevant.

[fengzhou-msft]

@alexvy86 I set up a vsonline VM and can reproduce your result. azure-cli can be installed successfully.

This is more likely an issue with the VM system implementation for lsb_release and uname. There's a discrepancy here.

[yonzhan]

@alexvy86 any update? Can we close this issue?

[alexvy86]

Well, I didn't report the issue... I haven't checked if the VMs created by VS Online now behave correctly (lsb_release -cs and uname -a not contradicting each other) but I'd say maybe you can close this issue, since it doesn't have to do with Azure cli directly?