[
https://issues.apache.org/jira/browse/AMBARI-24592?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16603484#comment-16603484
]
Hudson commented on AMBARI-24592:
---------------------------------
FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #9917 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/9917/])
AMBARI-24592 fix handling of stack defaults in blueprints (benyoka) (github:
[https://gitbox.apache.org/repos/asf?p=ambari.git&a=commit&h=b84ad9f03af89b7adabb22e14b429728246bf544])
* (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)
