Please note that until this issue is resolved, we won't be able to release 4.4.1.AM2 without some magic (read: lots of manual effort). All Boston MW Jenkins jobs are currently experiencing "ssh: connect to host filemgmt.jboss.org port 22: Connection refused". So until that's fixed, CI builds are on hold. Apologies, Nick ---------- Forwarded message ---------- From: Nick Boldt <nboldt(a)redhat.com&gt; Date: Thu, Jul 21, 2016 at 12:26 PM Subject: Re: [engineering.redhat.com #412491] Connection refused when ssh'ing to filemgmt.jboss.org from Jenkins To: eng-ops(a)redhat.com Cc: Lars Heinemann <lheinema(a)redhat.com&gt; To clarify, this issue doesn't block JBIDE-22766. But it DOES block us getting NEW builds published such that QE can test them. Please escalate -- this is quite urgent. On Thu, Jul 21, 2016 at 10:34 AM, Len DiMaggio via RT <eng-ops(a)redhat.com&gt; wrote: > Ticket <URL: https://engineering.redhat.com/rt/Ticket/Display.html?id=412491 > > > Can this issue be escalated? This is blocking product release testing. Thanks! > > https://issues.jboss.org/browse/JBIDE-22766 > > > > > > On Thu Jul 21 04:13:23 2016, pjanouse(a)redhat.com wrote: >> @eng-ops >> >> It looks like the whole MW QA lab (VLAN?) lost its network connectivity at >> least to the affected host filemgmt.jboss.org. Could you manage to fix it >> please? >> >> Thank you, >> >> Pavel > -- Nick Boldt :: JBoss by Red Hat Productization Lead :: JBoss Tools & Dev Studio http://nick.divbyzero.com -- Nick Boldt :: JBoss by Red Hat Productization Lead :: JBoss Tools & Dev Studio http://nick.divbyzero.com