[Bug 2136341] Re: [SRU] Include wsl-pro-service into wsl-recommends

[Carlos Nihelton]

** Description changed:

- WIP
+ [ Impact ]
+ * Users relying on Ubuntu Pro for WSL to automatically pro-attach their WSL instances any time, including first boot, as currently supported by Noble and later would be surprised with the lack of such feature in the upcoming images of Jammy and Focal to be published in the new format outside of the MS Store.
+ 
+ * Since we're already making the seeds of the older LTSes with the latest already published in that format compatible with each other, this is an opportunity to introduce this key offering in a less-surprising way.
+ * This is specially attractive to companies, where workloads are more likely to require older releases in specific cases, for which Ubuntu Pro is a necessary measure.
+ * For users not relying on Pro for WSL this unit is mostly inert, apart from frequent logs to the journal.
+ 
+ 
+ [ Test Plan ]
+ 
+ 1. Record the system status (systemctl status) after a regular boot first to ensure the system was already healthy. If in doubt, create a new, fresh, instance of Jammy with no startup issues. The 'systemctl status' should consistently show 'running' (and not 'degraded').
+ 2. Enable proposed and make sure to have wsl-pro-service implicitly installed by doing an 'apt update && apt upgrade -y';
+ 3. Reboot the instance a few times by exiting out of it and running 'wsl.exe --shutdown' on Windows.
+ 4. Restart the instance a few times, noticing whether boot time is affected or not by the updates and if the output of 'systemctl status' becomes 'degraded' or not.
+ 
+ The expected result is 'systemctl status' continuing to show 'running'
+ and no correlation between boot time and the update.
+ 
+ NOTE: Specific tests of wsl-pro-service were carried out in its own SRU.
+ Refer to LP: https://bugs.launchpad.net/ubuntu/+source/wsl-pro-
+ service/+bug/2133940.
+ 
+ 
+ [ Where problems could occur ]
+ * Since wsl-pro-service ships a systemd unit, boot time could increased or system startup could become degraded (as seen by 'systemctl status') if the unit and binary were not carefully crafted with that in mind.
+ 
+ 
+ [ Other Info ]
+ 
+ * This SRU completes the work to make Jammy for WSL images compatible with Noble and later.
+ * The changes herein proposed are a direct effect of running the './update' script part of the 'ubuntu-meta' source package (the standard way to synchronize it with the current state of the seed), excluding changes to the desktop meta-package for RISC-V because they are unrelated to WSL and I'm not aware of the needs for such changes. If they are needed, in fact they must be presented in a specific SRU.

** Changed in: ubuntu-meta (Ubuntu Jammy)
       Status: New => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to ubuntu-meta in Ubuntu.
https://bugs.launchpad.net/bugs/2136341

Title:
  [SRU] Include wsl-pro-service into wsl-recommends

Status in ubuntu-meta package in Ubuntu:
  New
Status in ubuntu-meta source package in Jammy:
  Confirmed

Bug description:
  [ Impact ]
  * Users relying on Ubuntu Pro for WSL to automatically pro-attach their WSL instances any time, including first boot, as currently supported by Noble and later would be surprised with the lack of such feature in the upcoming images of Jammy and Focal to be published in the new format outside of the MS Store.

  * Since we're already making the seeds of the older LTSes with the latest already published in that format compatible with each other, this is an opportunity to introduce this key offering in a less-surprising way.
  * This is specially attractive to companies, where workloads are more likely to require older releases in specific cases, for which Ubuntu Pro is a necessary measure.
  * For users not relying on Pro for WSL this unit is mostly inert, apart from frequent logs to the journal.

  
  [ Test Plan ]

  1. Record the system status (systemctl status) after a regular boot first to ensure the system was already healthy. If in doubt, create a new, fresh, instance of Jammy with no startup issues. The 'systemctl status' should consistently show 'running' (and not 'degraded').
  2. Enable proposed and make sure to have wsl-pro-service implicitly installed by doing an 'apt update && apt upgrade -y';
  3. Reboot the instance a few times by exiting out of it and running 'wsl.exe --shutdown' on Windows.
  4. Restart the instance a few times, noticing whether boot time is affected or not by the updates and if the output of 'systemctl status' becomes 'degraded' or not.

  The expected result is 'systemctl status' continuing to show 'running'
  and no correlation between boot time and the update.

  NOTE: Specific tests of wsl-pro-service were carried out in its own
  SRU. Refer to LP: https://bugs.launchpad.net/ubuntu/+source/wsl-pro-
  service/+bug/2133940.


  [ Where problems could occur ]
  * Since wsl-pro-service ships a systemd unit, boot time could increased or system startup could become degraded (as seen by 'systemctl status') if the unit and binary were not carefully crafted with that in mind.

  
  [ Other Info ]

  * This SRU completes the work to make Jammy for WSL images compatible with Noble and later.
  * The changes herein proposed are a direct effect of running the './update' script part of the 'ubuntu-meta' source package (the standard way to synchronize it with the current state of the seed), excluding changes to the desktop meta-package for RISC-V because they are unrelated to WSL and I'm not aware of the needs for such changes. If they are needed, in fact they must be presented in a specific SRU.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/2136341/+subscriptions