Your question means that I didn't clarify enough the test I followed and how it related to the original test plan proposed. The gap in understanding is more due WSL specifics than cloud-init itself.
The fundamental difference between what is proposed in the bug report and what I applied manually is: the availability of the Ubuntu-24.04 Windows application with the latest rootfs containing the patched version of this package (wsl-setup), which drastically simplifies the test setup. Of course that can only happen once this patch is merged and a new build of both the rootfs image and the Windows application submitted to the MS Store. So, the proposed test plan is complete and correct, but requires artifacts not available by the time this SRU bug is processed. It's rather applicable as a quality gate prior to the release of Windows app itself and a means of detecting future regression (our CI is capable of performing exactly that test case to detect regressions). The test I reported in https://bugs.launchpad.net/ubuntu/+source/wsl- setup/+bug/2065349/comments/6 is a manual workflow that behaves as if we had such up-to-date Windows app. It can be described in a high level structure as: 1. Set up a rootfs containing the latest version of this package (wsl-setup): - We create a new instance, update wsl-setup and export a snapshot with the minimum changes possible. Thus, cloud-init must be disabled (otherwise it would run automatically - as a systemd service - and cause more changes to the instance). Also. no other users are created as part of that set up. 2. Import that rootfs image emulating the behavior the Windows application would have (i.e. as if we run `ubuntu2404.exe`) - All the steps related to ensuring there is no cloud-init user-data files to be found, `wsl --import`, `adduser` and wait on cloud-init steps. Also the instance shutdown is needed to make the changes in `/etc/wsl.conf` to take effect. 3. Finally, perform the actual test, which is: ensure there is no `ubuntu` user pre-created and Wayland apps work. I'll edit that comment to clarify that structure, so others, not familiar with WSL specifics, may reason about what that procedure actually achieves. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2065349 Title: [SRU] Default user created by cloud-init confuses WSLg To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wsl-setup/+bug/2065349/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
