[
https://issues.apache.org/jira/browse/AMBARI-9989?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14353567#comment-14353567
]
Hadoop QA commented on AMBARI-9989:
-----------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12703488/AMBARI-9989.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 javac{color}. The applied patch does not increase the
total number of javac compiler warnings.
{color:green}+1 release audit{color}. The applied patch does not increase
the total number of release audit warnings.
{color:green}+1 core tests{color}. The patch passed unit tests in .
Test results:
https://builds.apache.org/job/Ambari-trunk-test-patch/1975//testReport/
Console output:
https://builds.apache.org/job/Ambari-trunk-test-patch/1975//console
This message is automatically generated.
> Falcon Quick links in Ambari are broken
> ---------------------------------------
>
> Key: AMBARI-9989
> URL: https://issues.apache.org/jira/browse/AMBARI-9989
> Project: Ambari
> Issue Type: Bug
> Components: ambari-web
> Affects Versions: 2.0.0
> Reporter: Antonenko Alexander
> Assignee: Antonenko Alexander
> Priority: Critical
> Fix For: 2.1.0
>
> Attachments: AMBARI-9989.patch
>
>
> From George Vetticaden:
> I have spun up a new HDP 2.2 with Ambari 1.7.0.
> In ambari, when I select Falcon Service --> Select Quick Links --> Falcon
> Web UI, the url that I get directed to is the following:
> http://centralregion03.xxx:15000/
> Which gives me the following error: Param user.name can't be empty.
> When I click on any of the tabs (Data Sets, processes, clusters), I get the
> same error. See screenshot.
> I can get around this by manually modifying the url to add the user.name
> query parameter like the following:
> http://centralregion03.xxx:15000/index.html?user.name
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)