[
https://issues.apache.org/jira/browse/BROOKLYN-103?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Aled Sage updated BROOKLYN-103:
-------------------------------
Description:
I deployed the blueprint shown below:
{noformat}
location:
aws-ec2:us-east-1:
osFamily: CentOS
name: JBoss 7 in AWS
services:
- type: brooklyn.entity.webapp.jboss.JBoss7Server
name: JBoss 7 Server
{noformat}
It chose the AMI RightImage_CentOS_7.0_x64_v14.1.4_EBS (ami-6224a40a).
Brooklyn was not able to reach the management http port because of the firewall
on the VM. I confirmed this was the case by running `sudo systemctl stop
firewalld` - I could then reach the port.
Note that the sledge-hammer configuration of `JcloudsLocation.STOP_IPTABLES`
would not work because it would try {{sudo service iptables stop}}, which
doesn't work.
{noformat}
[amp@ip-10-158-56-177 ~]$ sudo service iptables stop
Redirecting to /bin/systemctl stop iptables.service
Failed to issue method call: Unit iptables.service not loaded.
{noformat}
was:
I deployed the blueprint shown below:
location:
aws-ec2:us-east-1:
osFamily: CentOS
name: JBoss 7 in AWS
services:
- type: brooklyn.entity.webapp.jboss.JBoss7Server
name: JBoss 7 Server
It chose the AMI RightImage_CentOS_7.0_x64_v14.1.4_EBS (ami-6224a40a).
Brooklyn was not able to reach the management http port because of the firewall
on the VM. I confirmed this was the case by running `sudo systemctl stop
firewalld` - I could then reach the port.
Note that the sledge-hammer configuration of `JcloudsLocation.STOP_IPTABLES`
would not work because it would try `sudo service iptables stop`, which doesn't
work.
[amp@ip-10-158-56-177 ~]$ sudo service iptables stop
Redirecting to /bin/systemctl stop iptables.service
Failed to issue method call: Unit iptables.service not loaded.
> JBoss 7 server deploying to CentOS 7.0 failed (in aws-ec2:us-east-1)
> --------------------------------------------------------------------
>
> Key: BROOKLYN-103
> URL: https://issues.apache.org/jira/browse/BROOKLYN-103
> Project: Brooklyn
> Issue Type: Bug
> Affects Versions: 0.7.0
> Reporter: Aled Sage
>
> I deployed the blueprint shown below:
> {noformat}
> location:
> aws-ec2:us-east-1:
> osFamily: CentOS
> name: JBoss 7 in AWS
> services:
> - type: brooklyn.entity.webapp.jboss.JBoss7Server
> name: JBoss 7 Server
> {noformat}
> It chose the AMI RightImage_CentOS_7.0_x64_v14.1.4_EBS (ami-6224a40a).
> Brooklyn was not able to reach the management http port because of the
> firewall on the VM. I confirmed this was the case by running `sudo systemctl
> stop firewalld` - I could then reach the port.
> Note that the sledge-hammer configuration of `JcloudsLocation.STOP_IPTABLES`
> would not work because it would try {{sudo service iptables stop}}, which
> doesn't work.
> {noformat}
> [amp@ip-10-158-56-177 ~]$ sudo service iptables stop
> Redirecting to /bin/systemctl stop iptables.service
> Failed to issue method call: Unit iptables.service not loaded.
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
