Page MenuHomePhabricator

"snuggle" Cloud VPS project jessie deprecation
Closed, ResolvedPublic


The end of life of Debian Jessie is approaching in 2020 and we need to move to Debian Buster (or Stretch) before that date.

All instances in the snuggle project need to upgrade as soon as possible. Instances not upgraded by 2019-12-31 may be subject to deletion unless prior arrangements for an extended deadline has been approved by the Cloud VPS administration team.

Remaining Debian Jessie instances (live report):

Listed administrators are:

See also:

More info on current project instances is available via openstack browser


Due Date
Dec 31 2019, 11:59 PM

Event Timeline

StrikerBot created this task.

Ping @Halfak

The Cloud Services team would like to have Debian Jessie systems replaced with Debian Buster (or Stretch if necessary) before 2019-12-31. Please do respond of this task with comments if you know you will not be able to meet that target date or have additional questions about what to do or how to do it. Ideally you will create new instances in your Cloud VPS project, test them, and then migrate any final state data to the new instances before deleting the old Jessie instances. If you need more quota space in your project to create new instances in parallel with your existing instances please create a quota request task describing the increase you need and referencing this deprecation task.

Woops. I missed this. I'm on it.

I've been working on this, but I've run into some issues. wsgi on my new VM is hanging for 30 seconds without responding for every request so I'm stuck debugging this right now.

The 2020-04-25 EOL date for Debian Jessie is rapidly approaching. Projects where the status of migration is unknown maybe subject to forced instance shutdown on or before that date. Please reply with a rough timeline/plan for the resolution of this task.

Finally finished this off. Sorry for the delay.

BTW, the solution to the 30 second delay issue was: just delete the VM and make a new one!

BTW, the solution to the 30 second delay issue was: just delete the VM and make a new one!

Heh. This is the bigger hammer version of "have you tried turning it off and on again?". It is possible that your first instance ended up on one of the older cloudvirt servers which suffer from a variety of disk and cpu issues. We are scheduled to replace 9 of the oldest cloudvirts by the end of June which I have hopes will make unfortunate scheduling a bit less likely.