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

Hadoop QA commented on AMBARI-10175:
------------------------------------

{color:green}+1 overall{color}.  Here are the results of testing the latest 
attachment 
  http://issues.apache.org/jira/secure/attachment/12706537/AMBARI-10175.patch
  against trunk revision .

    {color:green}+1 @author{color}.  The patch does not contain any @author 
tags.

    {color:green}+1 tests included{color}.  The patch appears to include 3 new 
or modified test files.

    {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/2112//testReport/
Console output: 
https://builds.apache.org/job/Ambari-trunk-test-patch/2112//console

This message is automatically generated.

> Repo URL containing a ":" with no port number causes failed SSH Agent reg to 
> fail
> ---------------------------------------------------------------------------------
>
>                 Key: AMBARI-10175
>                 URL: https://issues.apache.org/jira/browse/AMBARI-10175
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-web
>    Affects Versions: 2.0.0
>            Reporter: Antonenko Alexander
>            Assignee: Antonenko Alexander
>             Fix For: 2.1.0
>
>         Attachments: 1_Screen Shot 2015-03-03 at 10.25.00 AM.png, 2_Screen 
> Shot 2015-03-03 at 10.26.48 AM.png, 3_Screen Shot 2015-03-03 at 10.29.33 
> AM.png, 5_Screen Shot 2015-03-03 at 10.24.32 AM.png, AMBARI-10175.patch
>
>
> *Issue*
> When entering a repository URL with a colon, but accidentally omitting the 
> port number, e.g. http://mirror.hortonworks.local:/hdp/HDP-2.2.0.0 instead of 
> http://mirror.hortonworks.local:8080/hdp/HDP-2.2.0.0 the following behavior 
> is observed:
> 1. Repo validation passes
> !1_Screen Shot 2015-03-03 at 10.25.00 AM.png|thumbnail!
> 2. Agent SSH bootstrap passes
> !2_Screen Shot 2015-03-03 at 10.26.48 AM.png|thumbnail!
> 3. Installation fails
> !3_Screen Shot 2015-03-03 at 10.29.33 AM.png|thumbnail!
> 4. When going back to the "Select Stack" and fixing the issue, validation 
> succeeds as expected
> 5. Agent SSH bootstrap fails due to HDP.repo and HDP-UTILS.repo being 
> malformed due to the missing port number.
> !5_Screen Shot 2015-03-03 at 10.24.32 AM.png|thumbnail!
> 6. User is stuck unless they manually remove all HDP.repo and HDP-UTILS.repo 
> files from the server
> :(
> See attached screenshot flow for each step.
> This is a valid Base url. Passes validation in Ambari UI and works just 
> fine...
> http://public-repo-1.hortonworks.com/HDP/centos6/2.x/GA/2.2.0.0
> This is also a valid Base url. Passes validation in Ambari UI BUT yum 
> chokes... so it's not until we get past Deploy and start trying to use the 
> .repo that yum fails...
> http://public-repo-1.hortonworks.com:/HDP/centos6/2.x/GA/2.2.0.0
> *Proposed Solution*: expanded URL validation should be implemented during 
> repository validation to prevent malformed but workable (depending on the 
> tool) URL's to be propegated.



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

Reply via email to