[jira] [Commented] (AMBARI-22680) Ambari web UI does not fail an invalid repo base URL during cluster installation
[ https://issues.apache.org/jira/browse/AMBARI-22680?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16300560#comment-16300560 ] Hudson commented on AMBARI-22680: - SUCCESS: Integrated in Jenkins build Ambari-trunk-Commit #8544 (See [https://builds.apache.org/job/Ambari-trunk-Commit/8544/]) AMBARI-22680 Ambari web UI does not fail an invalid repo base URL during (dili: [http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=a15fc7fc1ac70d3399a1b4046c3124dcc8cdbb11]) * (edit) ambari-server/src/main/java/org/apache/ambari/server/controller/internal/RepositoryResourceProvider.java * (edit) ambari-server/src/test/java/org/apache/ambari/server/controller/internal/RepositoryResourceProviderTest.java > Ambari web UI does not fail an invalid repo base URL during cluster > installation > > > Key: AMBARI-22680 > URL: https://issues.apache.org/jira/browse/AMBARI-22680 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: trunk >Reporter: Di Li >Assignee: Di Li > Fix For: trunk > > Attachments: AMBARI-22680.patch > > > This is because the Ambari server backend never validated anything. It just > simply sent back HTTP 200 as a dummy response. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-22680) Ambari web UI does not fail an invalid repo base URL during cluster installation
[ https://issues.apache.org/jira/browse/AMBARI-22680?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16300542#comment-16300542 ] Di Li commented on AMBARI-22680: pushed to trunk as https://git-wip-us.apache.org/repos/asf?p=ambari.git;a=commit;h=a15fc7fc1ac70d3399a1b4046c3124dcc8cdbb11 > Ambari web UI does not fail an invalid repo base URL during cluster > installation > > > Key: AMBARI-22680 > URL: https://issues.apache.org/jira/browse/AMBARI-22680 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: trunk >Reporter: Di Li >Assignee: Di Li > Fix For: trunk > > Attachments: AMBARI-22680.patch > > > This is because the Ambari server backend never validated anything. It just > simply sent back HTTP 200 as a dummy response. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-22680) Ambari web UI does not fail an invalid repo base URL during cluster installation
[ https://issues.apache.org/jira/browse/AMBARI-22680?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16300336#comment-16300336 ] Hadoop QA commented on AMBARI-22680: {color:green}+1 overall{color}. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12903099/AMBARI-22680.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 1 new or modified test files. {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-server. Console output: https://builds.apache.org/job/Ambari-trunk-test-patch/12877//console This message is automatically generated. > Ambari web UI does not fail an invalid repo base URL during cluster > installation > > > Key: AMBARI-22680 > URL: https://issues.apache.org/jira/browse/AMBARI-22680 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: trunk >Reporter: Di Li >Assignee: Di Li > Fix For: trunk > > Attachments: AMBARI-22680.patch > > > This is because the Ambari server backend never validated anything. It just > simply sent back HTTP 200 as a dummy response. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (AMBARI-22680) Ambari web UI does not fail an invalid repo base URL during cluster installation
[ https://issues.apache.org/jira/browse/AMBARI-22680?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16300130#comment-16300130 ] Hadoop QA commented on AMBARI-22680: {color:green}+1 overall{color}. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12903099/AMBARI-22680.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 1 new or modified test files. {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-server. Console output: https://builds.apache.org/job/Ambari-trunk-test-patch/12872//console This message is automatically generated. > Ambari web UI does not fail an invalid repo base URL during cluster > installation > > > Key: AMBARI-22680 > URL: https://issues.apache.org/jira/browse/AMBARI-22680 > Project: Ambari > Issue Type: Bug > Components: ambari-server >Affects Versions: trunk >Reporter: Di Li >Assignee: Di Li > Fix For: trunk > > Attachments: AMBARI-22680.patch > > > This is because the Ambari server backend never validated anything. It just > simply sent back HTTP 200 as a dummy response. -- This message was sent by Atlassian JIRA (v6.4.14#64029)