You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ambari.apache.org by "Hudson (JIRA)" <ji...@apache.org> on 2018/09/04 19:06:01 UTC
[jira] [Commented] (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:comment-tabpanel&focusedCommentId=16603464#comment-16603464 ]
Hudson commented on AMBARI-24592:
---------------------------------
SUCCESS: Integrated in Jenkins build Ambari-branch-2.7 #219 (See [https://builds.apache.org/job/Ambari-branch-2.7/219/])
AMBARI-24592 fix handling of stack defaults in blueprints (benyoka) (github: [https://gitbox.apache.org/repos/asf?p=ambari.git&a=commit&h=9cecd2a04db2103d057e09eab42b90a5218f9478])
* (edit) ambari-server/src/test/java/org/apache/ambari/server/controller/internal/BlueprintConfigurationProcessorTest.java
* (edit) ambari-server/src/main/java/org/apache/ambari/server/controller/internal/BlueprintConfigurationProcessor.java
> 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
>
> Time Spent: 1h
> Remaining Estimate: 0h
>
> 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)