[
https://issues.apache.org/jira/browse/AMBARI-22686?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16300678#comment-16300678
]
Hudson commented on AMBARI-22686:
---------------------------------
FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #8546 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/8546/])
AMBARI-22686. Disabled stack still appears in the UI if VDF is (swagle:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=e404100b99ffac8f14e36b46770466deeb5760d7])
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/api/services/AmbariMetaInfoTest.java
* (edit)
ambari-server/src/test/java/org/apache/ambari/server/controller/internal/RepositoryVersionResourceProviderTest.java
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/api/services/AmbariMetaInfo.java
> Disabled stack still appears in the UI if VDF is available
> ----------------------------------------------------------
>
> Key: AMBARI-22686
> URL: https://issues.apache.org/jira/browse/AMBARI-22686
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Affects Versions: 2.6.1
> Reporter: Siddharth Wagle
> Assignee: Siddharth Wagle
> Priority: Critical
> Fix For: 2.6.2
>
> Attachments: AMBARI-22686.patch
>
>
> Ambari-2.6.1, Ambari UI still shows HDP-2.3 as a stack that is active
> although the stack definition marks this as disabled.
> Seems like the UI does not make any calls to check stack active/in-active.
> The stacks returned from VDF endpoint are then used to get the repo URLs
> because the VDF returns the stack def as sub-resource which included the
> in-active stack.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
