[ https://issues.apache.org/jira/browse/AMBARI-15484?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15202899#comment-15202899 ]
Hadoop QA commented on AMBARI-15484: ------------------------------------ {color:green}+1 overall{color}. Here are the results of testing the latest attachment http://issues.apache.org/jira/secure/attachment/12794238/AMBARI-15484.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 2 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 ambari-server. Test results: https://builds.apache.org/job/Ambari-trunk-test-patch/5940//testReport/ Console output: https://builds.apache.org/job/Ambari-trunk-test-patch/5940//console This message is automatically generated. > enable ssl for ambari does not update the tez view url in tez-site.xml > ---------------------------------------------------------------------- > > Key: AMBARI-15484 > URL: https://issues.apache.org/jira/browse/AMBARI-15484 > Project: Ambari > Issue Type: Bug > Reporter: Andrew Onischuk > Assignee: Andrew Onischuk > Fix For: 2.2.2 > > Attachments: AMBARI-15484.patch > > > When one enables ssl for ambari we need to update the url set in tez.tez-ui > .history-url.base. We should update that to the new https url or atleast add > that to the enable ssl doc for ambari so the users know they have to update > it. -- This message was sent by Atlassian JIRA (v6.3.4#6332)