I did use this instance before and it seems that today i cannot ssh into, it looks like a networking issue since @akosiaris cannot access to it either. After diagnosing it a little bit with @GTirloni it indeed seems like a networking issue.
Description
Description
Event Timeline
This comment was removed by bd808.
Comment Actions
Instance in question is https://tools.wmflabs.org/openstack-browser/server/builder01.packaging.eqiad.wmflabs.
Comment Actions
The instance has role::builder applied. That role includes ::profile::base::firewall which applies ::base::firewall. My first guess was that the ferm rules this produces are not allowing ssh access to the host. To test this theory I added the role to a testing instance, forced a puppet run, and rebooted the server. This disproved my guess; ssh still works and all the expected bastion hosts are allowed to connect to port 22 by the generated iptables rules.
Comment Actions
Puppet is disabled on this VM:
$ ssh builder01.packaging.eqiad.wmflabs Linux builder01 4.9.0-8-amd64 #1 SMP Debian 4.9.110-3+deb9u6 (2018-10-08) x86_64 Debian GNU/Linux 9.3 (stretch) builder01 is a Docker images builder (builder) builder01 is a SystemTap development environment (systemtap::devserver) The last Puppet run was at Tue Jul 3 14:00:06 UTC 2018 (293441 minutes ago). Puppet is disabled. reason not specified
So it was missing this change https://gerrit.wikimedia.org/r/c/operations/puppet/+/461180
I manually edited /etc/ferm/conf.d/00_defs and added the new bastion IPs.