Page MenuHomePhabricator

Reach out to Cloud VPS project maintainers about Debian Bullseye deprecation
Closed, ResolvedPublic

Description

Contact maintainers of Cloud VPS projects with instances still running Debian Bullseye to migrate to a supported operating system.

List of projects(79 in all) as at June 4th, 2026

+++++ Message +++++++
Hello <Admin>,

We are reaching out to you because you are listed as an admin of the Cloud VPS <projects> below.

Some VMs in your project are still running on Debian Bullseye[0].

The migration from Debian Bullseye has been underway across Cloud VPS projects for a while now, and most affected projects have already completed their migrations.

Debian Bullseye will reach the end of its Long Term Support(LTS) on August 31, 2026.
In order to keep our platforms secure we need to move to Debian Bookworm or Trixie.

As part of this migration, it may be worth evaluating whether your workload is a good fit for Toolforge.
If feasible, migrating to Toolforge can reduce future maintenance burden, as operating system upgrades are handled by the platform.

All affected instances in these projects need to be upgraded by July 31st, 2026.[1]
After July 31st, instances that remain on Bullseye may be subject to deprecation or cleanup efforts starting August 1st, 2026.

<List of projects>

If you have already migrated your project, thank you!

Please reach out for help if you're unclear what this means, or how to upgrade[2].

[0]: https://os-deprecation.toolforge.org/
[1]: https://phabricator.wikimedia.org/T428196
[2]: https://wikitech.wikimedia.org/wiki/Portal:Toolforge/About_Toolforge#Communication_and_support

Event Timeline

We settled on December 1st, 2026 as the deadline for the migration/upgrade and January 1st, 2027 as the end of the grace period.

Hi Komla, I thought the deadline we discussed was end of September 2026. was there a subsequent conversation on this? thank you

@BLiviero-WMF sorry for the confusion.
I didn't understand it this way.

The current date was suggested on the draft message.

However, the message hasn't gone out yet.
Should I change it back to September, 2026.

I've shared the draft

Let me double check with a couple of other folks and get back to you! I
may have misunderstood myself

aputhin changed the task status from Open to In Progress.Jun 16 2026, 3:17 PM
aputhin triaged this task as High priority.
aputhin moved this task from Backlog to In progress on the tools-platform-team board.

The message has gone out to the admins

aputhin moved this task from In progress to Done on the tools-platform-team board.

Hi @Andrew , I received this e-mail as maintainer of the video CloudVPS project. The only remaining instance to migrate is the NFS one, I think we agreed long time ago this one would be for you, am I correct? If I'm wrong I can look at it, no problem.

Hi @Andrew , I received this e-mail as maintainer of the video CloudVPS project. The only remaining instance to migrate is the NFS one, I think we agreed long time ago this one would be for you, am I correct? If I'm wrong I can look at it, no problem.

You're right! I will take this on -- I just opened T429793. Do you have any concerns about when the downtime is? The most likely scenario is: a few minute outage followed by a reboot of all project VMs.

You're right! I will take this on -- I just opened T429793. Do you have any concerns about when the downtime is? The most likely scenario is: a few minute outage followed by a reboot of all project VMs.

Thank you ❤️ No concern for the downtime, I guess a small message on V2C talk page is enough to warn people about the maintenance :)

You're right! I will take this on -- I just opened T429793. Do you have any concerns about when the downtime is? The most likely scenario is: a few minute outage followed by a reboot of all project VMs.

Thank you ❤️ No concern for the downtime, I guess a small message on V2C talk page is enough to warn people about the maintenance :)

@Don-vip, this should be done; can you confirm that things are working properly again? The process was a bit bumpier than I hoped.

@Don-vip, this should be done; can you confirm that things are working properly again? The process was a bit bumpier than I hoped.

It seems to work fine. Thanks a lot!

In a different phabricator ticket it was pointed out that an upgrade-in-place may not be ideal, for reasons explained in the following document: https://wikitech.wikimedia.org/wiki/News/2025_Cloud_VPS_Bullseye_deprecation#Can_I_upgrade_an_existing_VM_in-place,_instead_of_re-creating_it_with_a_newer_Debian_

How can I make sure that maps-wma2 is updated? I might need some help with this. I suppose step one is to create a new VPS "maps-wma3" and reinstall everything there, tests it, and switch over to it once it is confirmed to work,

@dschwen please create a task for maps-wma2 and tag it with: Cloud-VPS (Debian Bullseye Deprecation)

The team will work with you to complete the migration.