Bug 1225075 - WSL: console starts as non-root in SLE
Summary: WSL: console starts as non-root in SLE
Status: NEW
Alias: None
Product: PUBLIC SUSE Linux Enterprise Server 15 SP6
Classification: openSUSE
Component: WSL (show other bugs)
Version: unspecified
Hardware: x86 Other
: P3 - Medium : Normal
Target Milestone: ---
Assignee: E-mail List
QA Contact: QE Containers and Public Cloud team qa-c
URL: https://openqa.suse.de/tests/14413970...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-05-23 07:35 UTC by Evgueni Tchubykalo
Modified: 2024-06-05 14:39 UTC (History)
3 users (show)

See Also:
Found By: openQA
Services Priority:
Business Priority:
Blocker: Yes
Marketing QA Status: ---
IT Deployment: ---
lubos.kocman: needinfo? (qa-c)

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Evgueni Tchubykalo 2024-05-23 07:35:21 UTC 
WSL console starts as non-root in SLE15sp6

Before, it was expected that the WSL console would start as root, as seen here: 
https://openqa.suse.de/tests/14319158#step/enable_systemd/10




## Reproducible

Fails since (at least) Build [2.334](https://openqa.suse.de/tests/14329712)


## Expected result

Last good: [2.333](https://openqa.suse.de/tests/14319158) (or more recent)


## Further details

Always latest result in this scenario: [latest](https://openqa.suse.de/tests/latest?arch=x86_64&distri=sle&flavor=Windows+10+UEFI&machine=win10_uefi&test=wsl2-main%2Bsystemd&version=15-SP6)
Comment 1 Lubos Kocman 2024-06-05 14:37:24 UTC 
Update from WSL meetign on June 5. 

This is  preferred and expected behaviour.
The root login is bit unexpected based on the overall feedback on the call.

Please adjust needles to the non-root login as expected behavior.

Root should be only used as a fallback (e.g. by skipping yast2-firstboot) in case there is no other user account.

Thank you
Comment 2 Lubos Kocman 2024-06-05 14:39:33 UTC 
Isn't it perhaps that on the old test suite, the user creation in firstboot was not successfuly done? Or the dialog was skipped or something.