brooklyn-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aled Sage (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (BROOKLYN-452) Brooklyn may fail to deploy with certain CentOS 7 images
Date Tue, 11 Apr 2017 09:37:41 GMT

     [ 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)

Mime
View raw message