Mailing-List: contact dev-help@ambari.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ambari.apache.org
Date: Mon, 23 Mar 2015 14:22:13 +0000 (UTC)
From: "Antonenko Alexander (JIRA)" <jira@apache.org>
To: dev@ambari.apache.org
Message-ID: <JIRA.12784825.1427120509000.6418.1427120533216@Atlassian.JIRA>
In-Reply-To: <JIRA.12784825.1427120509000@Atlassian.JIRA>
References: <JIRA.12784825.1427120509000@Atlassian.JIRA>
 <JIRA.12784825.1427120509026@arcas>
Subject: [jira] [Created] (AMBARI-10175) Repo URL containing a ":" with no
 port number causes failed SSH Agent reg to fail
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Antonenko Alexander created AMBARI-10175:
--------------------------------------------

             Summary: 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


*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)