[
https://issues.apache.org/jira/browse/KNOX-2675?focusedWorklogId=660209&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-660209
]
ASF GitHub Bot logged work on KNOX-2675:
----------------------------------------
Author: ASF GitHub Bot
Created on: 05/Oct/21 10:33
Start Date: 05/Oct/21 10:33
Worklog Time Spent: 10m
Work Description: dionusos opened a new pull request #506:
URL: https://github.com/apache/knox/pull/506
(It is very **important** that you created an Apache Knox JIRA for this
change and that the PR title/commit message includes the Apache Knox JIRA ID!)
## What changes were proposed in this pull request?
Added a new rewrite rule which replaces the internal Yarn url to a one
using Knox gateway
## How was this patch tested?
I had an environment with Knox and Oozie. I edited the
/var/lib/knox/gateway/data/services/oozie/5.0.0/rewrite.xml by adding the
changes described in this commit. Then I added a new line to
/var/lib/knox/gateway/conf/topologies/some-topology.xml to force Knox to
redeploy the affected topology. Then I navigated to
https://knox-gateway-host:8443/gateway/some-topology/oozie/, logged in, went to
"All Jobs", selected one, selected the action and on the "Action info" tab I
saw that Console URL is a Knox url.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 660209)
Remaining Estimate: 0h
Time Spent: 10m
> 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ó
> Priority: Major
> Time Spent: 10m
> 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)
