Unbound variable error from the latest version of dotnet-install.sh

[ujpandey]

The script exits with error due to an unbound variable. The code there seems to be assuming that the variable is set but that's only true if the download failed as of this commit which unsets the variables explicitly when starting the download.

On MacOS:

./dotnet-install.sh -c Current
dotnet-install: Note that the intended use of this script is for Continuous Integration (CI) scenarios, where:
dotnet-install: - The SDK needs to be installed without user interaction and without admin rights.
dotnet-install: - The SDK installation doesn't need to persist across multiple CI runs.
dotnet-install: To set up a development environment or to run apps, use installers rather than this script. Visit https://dotnet.microsoft.com/download to get the installer.

dotnet-install: Downloading primary link https://dotnetcli.azureedge.net/dotnet/Sdk/5.0.102/dotnet-sdk-5.0.102-osx-x64.tar.gz
./dotnet-install.sh: line 908: http_code: unbound variable

On Linux:

./dotnet-install.sh -c Current
dotnet-install: Note that the intended use of this script is for Continuous Integration (CI) scenarios, where:
dotnet-install: - The SDK needs to be installed without user interaction and without admin rights.
dotnet-install: - The SDK installation doesn't need to persist across multiple CI runs.
dotnet-install: To set up a development environment or to run apps, use installers rather than this script. Visit https://dotnet.microsoft.com/download to get the installer.

dotnet-install: Downloading primary link https://dotnetcli.azureedge.net/dotnet/Sdk/5.0.102/dotnet-sdk-5.0.102-linux-x64.tar.gz
./dotnet-install.sh: line 908: http_code: unbound variable

[BruceForstall]

@bozturkMSFT

[danmoseley]

@bozturkMSFT it would be good to understand how this bug made it through validation, as it is taking out our builds, what are your thoughts? Perhaps there's some more validation we can add.

[dougbu]

/fyi @dotnet/aspnet-build

[dougbu]

Offline is fine but I would appreciate a root cause analysis, not of the bug itself but of the rollout containing the bug.

[dave-yotta]

This has broken our deployments and halted building images in dev - when will the fix be rolled out? Very lucky production was not due to go out today! We use roslyn in production so the sdk is neccesary.