Last modified: 2012-08-27 15:02:21 UTC
As part of Bug 38777 - Regenerate deployment-bastion I have create a new instance named deployment-bastion. It uses a Precise image and s1.small (1CPU, 1GB RAM, 80G storage). When trying to connect to it I am rejected by ssh despite having rebooted the instance: $ ssh deployment-bastion.pmtpa.wmflabs If you are having access problems, please see: https://labsconsole.wikimedia.org/wiki/Access#Accessing_public_and_private_instances channel 0: open failed: administratively prohibited: open failed ssh_exchange_identification: Connection closed by remote host $
Got fixed somehow. Might be related to that instance getting corrupted at one point.
reopening, wrong bug. So that is indeed the new instance but it does not let us in :(
Running the ssh proxy command with verbose gives: debug1: channel_connect_stdio_fwd deployment-bastion.pmtpa.wmflabs:22 debug1: channel 0: new [stdio-forward] debug1: getpeername failed: Bad file descriptor Indeed, there is no host entry for deployment-bastion : hashar@bastion1:~$ host deployment-dbdump deployment-dbdump.pmtpa.wmflabs has address 10.4.0.56 hashar@bastion1:~$ host deployment-bastion Host deployment-bastion not found: 3(NXDOMAIN) hashar@bastion1:~$
Changed summary to: "labs DNS lacks an entry for deployment-bastion.pmtpa.wmflabs"
Need ops to create the DNS entry.
Not terribly urgent so lowering priority. We are still using deployment-dbdump so a possible way to fix the issue is to just recreate the instance. I let it around so ops could eventually find out what failed when inserting the DNS entry.
I have killed the instance and recreating it.
Still the same issue, so we need ops to update the DNS entry.
This has been fixed over the month of Augsut 2012.
