Debian Stretch's security support ends in mid 2022, and the Foundation's
OS policy already discourages use of existing Stretch machines. That
means that it's time for all project admins to start rebuilding your VMs
with Bullseye (or, if you must, Buster.)
Any webservices running in Kubernetes created in the last year or two
are most likely using Buster images already, so there's no action needed
for those. Older kubernetes jobs should be refreshed to use more modern
images whenever possible.
If you are still using the grid engine for webservices, we strongly
encourage you to migrate your jobs to Kubernetes. For other grid uses,
watch this space for future announcements about grid engine migration;
we don't yet have a solution prepared for that.
Details about the what and why for this process can be found here:
Here is the deprecation timeline:
March 2021: Stretch VM creation disabled in most projects
July 6, 2021: Active support of Stretch ends, Stretch moves into LTS
<- You are Here ->
January 1st, 2022: Stretch VM creation disabled in all projects,
deprecation nagging begins in earnest. Stretch alternatives will be
available for tool migration in Toolforge
May 1, 2022: All active Stretch VMs will be shut down (but not deleted)
by WMCS admins. This includes Toolforge grid exec nodes.
June 30, 2022: LTS support for Debian Stretch ends, all Stretch VMs will
be deleted by WMCS admins
Rstudio has an interest in system users existing that make it difficult to
upgrade in PAWS, which doesn't have the same ideas about system users.
Currently the single user container is blocked from being upgraded by
Rstudio. There are some more Rstudio specific details in
One simple solution would be to remove Rstudio. At the moment there is not
a clear path forward for keeping it as a part of PAWS.
Are there any opinions on this approach?
*Vivian Rook (They/Them)*
Site Reliability Engineer
Wikimedia Foundation <https://wikimediafoundation.org/>
WMCS will be migrating the remaining Toolforge tools running on Stretch
grid to Buster grid tomorrow(2nd June, 2022).
This has become necessary as the deadline for long term support(including
security updates) for Stretch comes to an end this month(June 2022).
=== What Do I Have To Do ===
Unless your tool starts failing on Buster grid, you don't have to do
If your tool can only work on Stretch grid, you can temporarily move it
back to Stretch grid with the following commands(while you work to port it
to Buster grid or kubernetes)
Stop and Start the tool with *-release=stretch* flag
Example: *webservice stop*; *webservice start -release=stretch*
Add *-release=stretch* to jsub command
Example: *jsub -release=stretch ...*
If you need further assistance, kindly reach out to us via our
Seyram Komla Sapaty
Wikimedia Cloud Services