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

Attila Sasvári commented on OOZIE-3725:
---------------------------------------

[~dionusos] unfortunately, I don't have enough/predictable bandwidth to work on 
Oozie. 

Last night, I noticed a problem when running tests in core/ on Ubuntu 22.04.5 
LTS in WSL using hadoop 2.6.0
- during running tests in TestSubmitXCommand, the JVM terminated
- test logs indicated an exception when trying to clean up logs 
https://github.com/apache/hadoop/blob/e3496499ecb8d220fba99dc5ed4c99c8f9e33bb1/hadoop-yarn-project/hadoop-yarn/hadoop-yarn-server/hadoop-yarn-server-nodemanager/src/main/java/org/apache/hadoop/yarn/server/nodemanager/containermanager/launcher/ContainerLaunch.java#L433
  
- bumped hadoop version to 2.8.5 and reran TestSubmitXCommand tests in /core, 
tests passed.

I've attached OOZIE-3725-4.patch to see whether bumping the hadoop version 
fixes the CI problem. Based on 
https://ci-hadoop.apache.org/job/PreCommit-OOZIE-Build/232/console, more tests 
pass now and result is reported back (surefire plugin is not terminated). On 
the other hand, the errors and failures (especially in sharelib) are 
concerning. The project doesn't seem to be in a releaseable state.

(In OOZIE-3725-3.patch, added dependency exclusions in webapp because a distro 
using the uber profile otherwise couldn't be generated.)

> Drop support for the webui
> --------------------------
>
>                 Key: OOZIE-3725
>                 URL: https://issues.apache.org/jira/browse/OOZIE-3725
>             Project: Oozie
>          Issue Type: Task
>            Reporter: Gézapeti
>            Assignee: Gézapeti
>            Priority: Major
>         Attachments: OOZIE-3725-1.patch, OOZIE-3725-2.patch, 
> OOZIE-3725-3.patch, OOZIE-3725-4.patch
>
>
> The recent CVEs were reported on the oozie webui which is old and 
> unmaintained. 
> Let's drop support for it.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to