[ 
https://issues.apache.org/jira/browse/AMBARI-10389?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14484264#comment-14484264
 ] 

Hadoop QA commented on AMBARI-10389:
------------------------------------

{color:red}-1 overall{color}.  Here are the results of testing the latest 
attachment 
  
http://issues.apache.org/jira/secure/attachment/12723760/AMBARI-10389.001.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:red}-1 core tests{color}.  The test build failed in ambari-server 

Test results: 
https://builds.apache.org/job/Ambari-trunk-test-patch/2274//testReport/
Console output: 
https://builds.apache.org/job/Ambari-trunk-test-patch/2274//console

This message is automatically generated.

> NFS Gateway breaks Windows installation
> ---------------------------------------
>
>                 Key: AMBARI-10389
>                 URL: https://issues.apache.org/jira/browse/AMBARI-10389
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-server
>    Affects Versions: 2.1.0
>            Reporter: Brandon Li
>            Assignee: Brandon Li
>             Fix For: 2.1.0
>
>         Attachments: AMBARI-10389.001.patch
>
>
> [~jluniya] pointed out:
> {quote}
> NFS Gateway is not supported for Windows. Hence I removed NFS Gateway 
> component from the HDPWIN stack definition.
> However the current ambari-web changes are very tightly integrated and do not 
> check for the case where NFS Gateway component is present in the selected 
> stack. Hence 
> 1. During Customize Services, I see a section for "NFS Gateway" config 
> properties to be displayed for Windows
> 2. During Review step in the installation wizard, the wizard is looking for 
> NFS Gateway component and throws a null exception.
> Can you add additional checks in the ambari-web to handle the scenario of NFS 
> Gateway component not being present more gracefully. Apart from Windows, this 
> potentially might be a valid scenario for other vendors who dont have to 
> support an NFS Gateway.
> {quote}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to