@Lcanasdiaz As Korma is still operational in read only mode, Unbreak now! isn't the appropriate.

Furthermore, assign tasks with high priority is counterproductive: you could let think people able to fix the issue someone is already working on that, and so you decrease pick up chances.

Just in case: docs on how to access wmflabs.org instances are at https://wikitech.wikimedia.org/wiki/Help:Access

The server korma.wmflabs.org listens publicly to 22 and accept incoming SSH connections.

Could you try from the remote machine ssh -vvv theusernameforrsync@korma.wmflabs.org?

alex@alex-laptop:~$ ssh korma.wmflabs.org 
Linux novaproxy-01 3.16.0-4-amd64 #1 SMP Debian 3.16.7-ckt20-1+deb8u4 (2016-02-29) x86_64
Debian GNU/Linux 8.1 (jessie)
The last Puppet run was at Mon Mar 28 14:01:53 UTC 2016 (9 minutes ago). 
Last login: Mon Mar 28 14:10:42 2016 from bastion-01.bastion.eqiad.wmflabs
krenair@novaproxy-01:~$

You can't SSH there, it's pointing to the proxy which is a highly restricted system.

krenair@novaproxy-01:~$ sudo sqlite3 /etc/dynamicproxy-api/data.db
SQLite version 3.8.7.1 2014-10-29 13:59:56
Enter ".help" for usage hints.
sqlite> .schema route
CREATE TABLE route (
	id INTEGER NOT NULL, 
	domain VARCHAR(256), 
	project_id INTEGER, 
	PRIMARY KEY (id), 
	UNIQUE (domain), 
	FOREIGN KEY(project_id) REFERENCES project (id)
);
sqlite> .schema backend
CREATE TABLE backend (
	id INTEGER NOT NULL, 
	url VARCHAR(256), 
	route_id INTEGER, 
	PRIMARY KEY (id), 
	FOREIGN KEY(route_id) REFERENCES route (id)
);
sqlite> select backend.url from backend, route where backend.route_id = route.id and route.domain = 'korma.wmflabs.org.';
http://contributors-metrics.contributors.eqiad.wmflabs:80

Now you could SSH to that instance via the bastion, but according to nova, that instance also has public IP 208.80.155.168.

In T131046#2154530, @Dereckson wrote:

@Lcanasdiaz As Korma is still operational in read only mode, Unbreak now! isn't the appropriate.

I didn't know Korma is in read only mode :_O

Furthermore, assign tasks with high priority is counterproductive: you could let think people able to fix the issue someone is already working on that, and so you decrease pick up chances.

Understood. Thank you for the tip :)