[
https://issues.apache.org/jira/browse/AMBARI-25040?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16719365#comment-16719365
]
Hudson commented on AMBARI-25040:
---------------------------------
SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #10380 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/10380/])
AMBARI-25040. Handle blueprint/VDF stack version mismatch (#2719) (github:
[https://gitbox.apache.org/repos/asf?p=ambari.git&a=commit&h=6c9c06c34bd31562962e5e956c201db3990fc8db])
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/topology/AmbariContext.java
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/topology/addservice/RequestValidatorTest.java
* (add)
ambari-server/src/test/java/org/apache/ambari/server/utils/Assertions.java
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/topology/AmbariContextTest.java
> Handle blueprint/VDF stack version mismatch
> -------------------------------------------
>
> Key: AMBARI-25040
> URL: https://issues.apache.org/jira/browse/AMBARI-25040
> Project: Ambari
> Issue Type: Improvement
> Components: ambari-server
> Affects Versions: 2.5.0
> Reporter: Doroszlai, Attila
> Assignee: Doroszlai, Attila
> Priority: Major
> Labels: pull-request-available
> Fix For: 2.8.0
>
> Time Spent: 0.5h
> Remaining Estimate: 0h
>
> If a repository version is explicitly specified in the cluster creation
> request (using {{repository_version_id}} or {{repository_version}}), then
> Ambari should reject the cluster creation request if the blueprint and the
> VDF stacks are different (eg. HDP 2.6 vs HDP 3.0). If it allowed deployment,
> the cluster would run into various errors due to the mismatch (eg. UI
> glitches, attempting to install the wrong package, etc.)
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
