Issue: UP4W can set the default WSL instance to be one that is not running the wsl-pro.service.

[wck0]

Is there an existing issue for this?

• I have searched the existing issues and found none that matched mine

Describe the issue

Landscape server will only make SetDefault gRPC calls with the instance names that are actually registered in Landscape. However, UP4W will process those gRPC commands and set any installed WSL image to be the default one.

I tested also with the Uninstall command, and in this case UP4W is indeed checking something and producing a log message like distro not in database.

Steps to reproduce it

Have some WSL instance installed on the Windows machine that is not managed by Landscape and does not have the wsl-pro.service installed on it.
Have another that is managed by Landscape with the wsl-pro.service running on in.
Manually set the Landscape managed one to be the default.
Make a SetDefault gRPC call to UP4W with the name of the WSL instance without wsl-pro.service.
Observe that one is now the default.

Installed versions

• Windows version: Version 10.0.22631.3880
• WSL version: 2
• Windows application version: v0.1.4-394-g1b1b88eb-dirty
• WSL distribution: Ubuntu, Ubuntu-22.04, kali-linux
• WSL OS: same as above
• ubuntu wsl service version: N/A

System logs

There are no relevant log entries.

Double check your logs

• I have redacted any sensitive information from the logs

Additional information

No response