You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@brooklyn.apache.org by "Aled Sage (JIRA)" <ji...@apache.org> on 2017/04/11 09:37:41 UTC
[jira] [Resolved] (BROOKLYN-452) Brooklyn may fail to deploy with
certain CentOS 7 images
[ https://issues.apache.org/jira/browse/BROOKLYN-452?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Aled Sage resolved BROOKLYN-452.
--------------------------------
Resolution: Fixed
Assignee: Yavor Yanchev
Fix Version/s: 0.11.0
I think that https://github.com/apache/brooklyn-server/pull/591 fixes it, rather than just working around it. Marking as fixed.
> Brooklyn may fail to deploy with certain CentOS 7 images
> --------------------------------------------------------
>
> Key: BROOKLYN-452
> URL: https://issues.apache.org/jira/browse/BROOKLYN-452
> Project: Brooklyn
> Issue Type: Improvement
> Reporter: Yavor Yanchev
> Assignee: Yavor Yanchev
> Fix For: 0.11.0
>
>
> There is a change made by RedHat [1] [2] which landed in CentOS 7 as well. It prevents the normal deployment due to change in the sudo configuration.
> The reported behavior is observed when Brooklyn is configured not to use jclouds for the initial ssh-based setup. Brooklyn is not using jclouds if *useJcloudsSshInit* parameter is set to *false*
> [1] https://bugzilla.redhat.com/show_bug.cgi?id=1196451
> [2] https://rhn.redhat.com/errata/RHSA-2016-2593.html
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)