You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@knox.apache.org by "Sandeep More (Jira)" <ji...@apache.org> on 2021/10/05 15:07:00 UTC

[jira] [Assigned] (KNOX-2675) Oozie Console URL on the web UI should be a Knox URL

     [ https://issues.apache.org/jira/browse/KNOX-2675?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Sandeep More reassigned KNOX-2675:
----------------------------------

    Assignee: Dénes Bodó

> Oozie Console URL on the web UI should be a Knox URL
> ----------------------------------------------------
>
>                 Key: KNOX-2675
>                 URL: https://issues.apache.org/jira/browse/KNOX-2675
>             Project: Apache Knox
>          Issue Type: Improvement
>    Affects Versions: 1.4.0
>            Reporter: Dénes Bodó
>            Assignee: Dénes Bodó
>            Priority: Major
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> When I open the Oozie web UI through Knox gateway and navigate to a workflow's action details then I see the Console URL field contains the cluster's internal hostname instead of a Knox gateway url. Here is an example json result from Oozie through Knox:
> {noformat}
> {
>     "appName":"some_oozie_application",
>     ...
>     "actions":[
>         {...},
>         {
>             ...
>             "consoleUrl":"https://some_internal_domain_name:8090/proxy/application_1632125050865_0003/",
>             ...
>         },
>         {...}
>     ],
>     "status":"SUCCEEDED",
>     "group":null
> } {noformat}
> The desired form should be for the consoleUrl field something like this:
> {noformat}
> https://externally_available_knox_domain_name:8443/gateway/cdp-proxy/yarn/cluster/app/application_1632125050865_0003/ {noformat}
> The proposed solution contains Yarn UI v1 URL because the Yarn UI v2 contains a hash mark which cannot be used. See KNOX-2676



--
This message was sent by Atlassian Jira
(v8.3.4#803005)