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

Hudson commented on AMBARI-9529:
--------------------------------

FAILURE: Integrated in Ambari-trunk-Commit #1739 (See 
[https://builds.apache.org/job/Ambari-trunk-Commit/1739/])
AMBARI-9529 Ambari view - View iframe pointing to invalid link when ambari url 
contains query parameters. (atkach) (atkach: 
http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=032bbd760fb4dae566734779f1b6999958a0ffcc)
* ambari-web/app/views/main/views/details.js
* ambari-web/test/routes/views_test.js
* ambari-web/app/routes/views.js
* ambari-web/app/assets/test/tests.js


> Ambari view - View iframe pointing to invalid link when ambari url contains 
> query parameters
> --------------------------------------------------------------------------------------------
>
>                 Key: AMBARI-9529
>                 URL: https://issues.apache.org/jira/browse/AMBARI-9529
>             Project: Ambari
>          Issue Type: Bug
>            Reporter: Sreenath Somarajapuram
>            Assignee: Andrii Tkach
>         Attachments: AMBARI-9529.patch, AMBARI-9529_v2.patch
>
>
> We are facing a problem with the  view iframe src.
> Problem
> On entering the following in the address bar
> http://ip:8080/#/main/views/<name>/<version>/<instance-name>?foo=bar
> instead of at-least pointing to
> http://ip:8080/views/<name>/<version>/<instance-name>
> the view iframe is pointing to
> http://ip:8080undefined ! (And our app doesn't load)
> Why it is a bug: Because there is a weird way make it work!
> To make it work: From the address bar first load 
> http://ip:8080/views/<name>/<version>/<instance-name>
> and then load 
> http://ip:8080/#/main/views/<name>/<version>/<instance-name>?foo=bar
> Result
> Intention is to pass a path as parameter. Because of this bug we are not able 
> to create link to a specific tez-ui page



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

Reply via email to