[
https://issues.apache.org/jira/browse/BROOKLYN-588?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16500009#comment-16500009
]
ASF GitHub Bot commented on BROOKLYN-588:
-----------------------------------------
Github user tbouron commented on a diff in the pull request:
https://github.com/apache/brooklyn-docs/pull/256#discussion_r192688576
--- Diff: guide/ops/troubleshooting/connectivity.md ---
@@ -104,8 +104,8 @@ example, execute `sudo iptables -n --list` and
`iptables -t nat -n --list`.
## Cloud firewalls
Some clouds offer a firewall service, where ports need to be explicitly
listed to be reachable.
-For example, [security groups for EC2-classic]
-(http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/using-network-security.html#ec2-classic-security-groups)
+For example,
+[security groups for
EC2-classic](http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/using-network-security.html)
--- End diff --
Why did you removed the anchor here? It is still valid.
Having said that, the section doesn't seem to have specificities to
firewalls. So the title probably need to change to `security groups for EC2`,
or be dropped all together
> SoftwareProcess download with curl can fail on CentOS 7.0 (TLS negotiation)
> ---------------------------------------------------------------------------
>
> Key: BROOKLYN-588
> URL: https://issues.apache.org/jira/browse/BROOKLYN-588
> Project: Brooklyn
> Issue Type: Bug
> Affects Versions: 0.12.0
> Reporter: Aled Sage
> Priority: Major
>
> When a {{SoftwareProcess}} entity needs to download an install artifact, it
> often uses curl.
> When running CentOS 7.0, this can fail. For example, when attempting to
> download something from github:
> {noformat}
> /usr/bin/curl
> curl: (37) Couldn't open file
> /home/users/amp/.brooklyn/repository/EtcdNode/2.3.1/etcd-v2.3.1-linux-amd64.tar.gz
> % Total % Received % Xferd Average Speed Time Time Time
> Current
> Dload Upload Total Spent Left Speed
> 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
> 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
> 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
> curl: (35) Peer reports incompatible or unsupported protocol version.
> % Total % Received % Xferd Average Speed Time Time Time
> Current
> Dload Upload Total Spent Left Speed
> 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
> 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
> 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0
> curl: (22) The requested URL returned error: 404 Not Found
> Could not retrieve etcd-v2.3.1-linux-amd64.tar.gz. Tried:
> file://$HOME/.brooklyn/repository/EtcdNode/2.3.1/etcd-v2.3.1-linux-amd64.tar.gz,
>
> https://github.com/coreos/etcd/releases/download/v2.3.1/etcd-v2.3.1-linux-amd64.tar.gz,
>
> http://downloads.cloudsoftcorp.com/brooklyn/repository/EtcdNode/2.3.1/etcd-v2.3.1-linux-amd64.tar.gz
> Executed
> /tmp/brooklyn-20180521-195405819-Dfo2-installing_EtcdNodeImpl_id_oe3.sh,
> result 9
> {noformat}
> This can happen when using a 'minimal' location in AWS (e.g. when just
> specifying the {{osFamily: centos}}, and not an explicit AMI, which defaults
> to a CentOS 7.0 AMI).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
