You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ambari.apache.org by "Hadoop QA (JIRA)" <ji...@apache.org> on 2017/12/21 21:26:00 UTC
[jira] [Commented] (AMBARI-22686) Disabled stack still appears in
the UI if VDF is available
[ https://issues.apache.org/jira/browse/AMBARI-22686?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16300561#comment-16300561 ]
Hadoop QA commented on AMBARI-22686:
------------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12903311/AMBARI-22686.patch
against trunk revision .
{color:red}-1 patch{color}. The patch command could not apply the patch.
Console output: https://builds.apache.org/job/Ambari-trunk-test-patch/12881//console
This message is automatically generated.
> 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)