brooklyn-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Thomas Bouron (JIRA)" <j...@apache.org>
Subject [jira] [Created] (BROOKLYN-151) Can't SSH - firewall active on Suse 11 SP3 Entreprise Server
Date Fri, 19 Jun 2015 16:07:00 GMT
Thomas Bouron created BROOKLYN-151:
--------------------------------------

             Summary: Can't SSH - firewall active on Suse 11 SP3 Entreprise Server
                 Key: BROOKLYN-151
                 URL: https://issues.apache.org/jira/browse/BROOKLYN-151
             Project: Brooklyn
          Issue Type: Bug
    Affects Versions: 0.7.0-M2
         Environment: Suse 11 SP3 Entreprise Server
            Reporter: Thomas Bouron


When Brooklyn finishes to provision the VM, it tries to connect over SSH to perform its actions.
On Suse 11 SP3 Entreprise Server, the default Suse firewall is enable by default, even if
the property {{brooklyn.location.named.my-location.stopIptables}} is set to {{true}}. This
cause the VM provisioning to fail.

To disable it, I had to run this manually to stop the service:
{code}
/sbin/SuSEfirewall2 stop
{code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message