Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id C565E200C76 for ; Fri, 7 Apr 2017 14:49:46 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id C3F6E160B97; Fri, 7 Apr 2017 12:49:46 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 14BA1160BA2 for ; Fri, 7 Apr 2017 14:49:45 +0200 (CEST) Received: (qmail 42188 invoked by uid 500); 7 Apr 2017 12:49:45 -0000 Mailing-List: contact issues-help@ambari.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@ambari.apache.org Delivered-To: mailing list issues@ambari.apache.org Received: (qmail 41930 invoked by uid 99); 7 Apr 2017 12:49:45 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 07 Apr 2017 12:49:45 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id 9B4721AA296 for ; Fri, 7 Apr 2017 12:49:44 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -100.002 X-Spam-Level: X-Spam-Status: No, score=-100.002 tagged_above=-999 required=6.31 tests=[RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id n1T5N6rfzyCI for ; Fri, 7 Apr 2017 12:49:43 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTP id 49CE55FC84 for ; Fri, 7 Apr 2017 12:49:43 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 90EE3E0D1C for ; Fri, 7 Apr 2017 12:49:42 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id E4F672406F for ; Fri, 7 Apr 2017 12:49:41 +0000 (UTC) Date: Fri, 7 Apr 2017 12:49:41 +0000 (UTC) From: "Hadoop QA (JIRA)" To: issues@ambari.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (AMBARI-20700) UI should use the URL as-given by the backend MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Fri, 07 Apr 2017 12:49:46 -0000 [ https://issues.apache.org/jira/browse/AMBARI-20700?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15960719#comment-15960719 ] Hadoop QA commented on AMBARI-20700: ------------------------------------ {color:red}-1 overall{color}. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12862437/AMBARI-20700.patch against trunk revision . {color:green}+1 @author{color}. The patch does not contain any @author tags. {color:red}-1 tests included{color}. The patch doesn't appear to include any new or modified tests. Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch. {color:green}+1 release audit{color}. The applied patch does not increase the total number of release audit warnings. {color:green}+1 javac{color}. The applied patch does not increase the total number of javac compiler warnings. {color:green}+1 core tests{color}. The patch passed unit tests in ambari-web. Test results: https://builds.apache.org/job/Ambari-trunk-test-patch/11331//testReport/ Console output: https://builds.apache.org/job/Ambari-trunk-test-patch/11331//console This message is automatically generated. > UI should use the URL as-given by the backend > --------------------------------------------- > > Key: AMBARI-20700 > URL: https://issues.apache.org/jira/browse/AMBARI-20700 > Project: Ambari > Issue Type: Bug > Components: ambari-web > Affects Versions: 2.5.1 > Reporter: Richard Zang > Assignee: Richard Zang > Fix For: 2.5.1 > > Attachments: AMBARI-20700.patch > > > The UI should be using repositories based on VDF exactly as the backend is presenting them. There should be no need to assume that HDP and HDP-UTILS are always going to be there. > Other developers have reported that using their own VDF also does not change the base URL to what is defined in the VDF. > Any fixes made should be consistent between the installer and the Admin view that manages repositories. -- This message was sent by Atlassian JIRA (v6.3.15#6346)