Page MenuHomePhabricator

cloudvps: utrs project trusty deprecation
Closed, ResolvedPublic


Ubuntu Trusty is no longer available in Cloud VPS since Nov 2017 for new instances. However, the EOL of Trusty is approaching in 2019 and we need to move to Debian Stretch before that date.

All instances in the utrs project needs to upgrade as soon as possible.

The list of affected VMs is:

  • utrs-database.utrs.eqiad.wmflabs
  • utrs-production.utrs.eqiad.wmflabs

Listed administrator are:

More info in openstack browser:

Event Timeline

Krenair triaged this task as Medium priority.Sep 17 2018, 4:59 PM
Krenair created this task.

Hey @DeltaQuad @TParis! Just a friendly reminder that you should get rid of your Trusty instances as described in The deadline is 2018-12-18. Please get in contact if you need help.

Also, please assign this task to an individual.

Another ping. Deadline is approaching (2018-12-18).

@Krenair So to be clear, there is no more ubuntu available? And therefore the entire instance needs rebuilding?

Basically I have to fully backup everything, reinstall everything, and move the files over?

If so, it'll have to be done after Dec 4th, because I've got papers and exams to write.

Ping. Today is Friday and the deadline is Tuesday.

This comment was removed by AmandaNP.

Sorry, I missed your original comment. Ubuntu Trusty is the only Ubuntu version currently supported and has not been available for installation for some time now. No new version of Ubuntu is being made available, the only choices are Debian Jessie and Debian Stretch (Stretch is the recommended one).
In-place upgrades are never advisable or recommended, and I'm not sure it would be possible to do this from Ubuntu to Debian anyway. You should always be prepared to reinstall the servers.
This does imply installing the new server (including applications etc. from puppet), copying the data over from the old equivalent machine, moving traffic to the new one, and then shutting down the old one.

neither instance is showing up in my horizon view nor does it look like I have the ability to create a new instance.

Since you deleted this comment you may have figured this out but if not, check that your horizon view is set to look at the correct project (utrs) and in the correct region (eqiad1-r)

I don't even have access to the Account Creation tool instances that I'm also supposed have.

I believe that is the account-creation-assistance project rather than utrs? Those are all running Debian Jessie/Stretch so are fine as far as Trusty deprecation goes.

Yes, I just didn't see that I had to switch projects. I see it now.
We are just waiting for the floating IP to re associate to utrs-production2 instead of utrs-production. Not sure how long that will take.

In T204565#4826044, @DeltaQuad wrote:

We are just waiting for the floating IP to re associate to utrs-production2 instead of utrs-production. Not sure how long that will take.

It should be pretty much instant.

From IRC: There was previously an instance with both the proxy pointing at it, and also a floating IP attached. The proxy has been moved.

Sidenote: @Andrew something is weird with this floating IP that @DeltaQuad noted on IRC:

alex@alex-laptop:~$ ping
PING ( 56(84) bytes of data.
64 bytes from icmp_seq=1 ttl=48 time=82.0 ms
64 bytes from icmp_seq=2 ttl=48 time=82.8 ms
64 bytes from icmp_seq=3 ttl=48 time=124 ms
--- ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2003ms
rtt min/avg/max/mdev = 82.020/96.306/124.033/19.611 ms
alex@alex-laptop:~$ dig -x

; <<>> DiG 9.11.3-1ubuntu1.3-Ubuntu <<>> -x
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 24276
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1

; EDNS: version: 0, flags:; udp: 512

;; AUTHORITY SECTION:	1799	IN	SOA 1544823727 3596 600 86400 3600

;; Query time: 101 msec
;; WHEN: Sun Dec 16 02:21:43 GMT 2018
;; MSG SIZE  rcvd: 125

It also doesn't appear at

@Krenair I have finished moving them onto 2 small instances instead of mediums and deleted them. You can close this when you are done re floating ip.