You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ambari.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2018/09/04 14:25:00 UTC

[jira] [Updated] (AMBARI-24592) Blueprint installation stuck (cannot resolve cluster-env), continues after ambari-server restart

     [ https://issues.apache.org/jira/browse/AMBARI-24592?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

ASF GitHub Bot updated AMBARI-24592:
------------------------------------
    Labels: pull-request-available  (was: )

> Blueprint installation stuck (cannot resolve cluster-env), continues after ambari-server restart
> ------------------------------------------------------------------------------------------------
>
>                 Key: AMBARI-24592
>                 URL: https://issues.apache.org/jira/browse/AMBARI-24592
>             Project: Ambari
>          Issue Type: Bug
>    Affects Versions: 2.7.0, 2.7.1
>            Reporter: Balázs Bence Sári
>            Assignee: Balázs Bence Sári
>            Priority: Critical
>              Labels: pull-request-available
>             Fix For: 2.7.2
>
>
> The issue occurs with exported blueprints. These blueprints contain the stack defaults. When a new cluster is installed from such blueprint the *BlueprintConfigurationProcessor* falsely thinks it updates _cluster-env_ when setting the stack defaults.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)