AMBARI-26113: Switch the PhantomJS used by Karma tests to chromium-browser

[zRains]

What changes were proposed in this pull request?

With the arrival of the ambari-web upgrade PR: #3770 , PhantomJS is no longer sufficient to support future testing tasks, as its support for ES5 has been abandoned(#14506, #14458). The chromium-browser will provide ES5 syntax support and enable testing for more libraries. This will be one of the foundational steps in the overall ambari-web upgrade plan.

This PR will be divided into two modules: ambari-web and ambari-admin. PhantomJS will be completely removed, and some failing tests will be fixed.

How was this patch tested?

$ mvn -T 2C -am test -pl ambari-web -Dmaven.artifact.threads=10 -Drat.skip
$ mvn -T 2C -am test -pl ambari-admin -Dmaven.artifact.threads=10 -Drat.skip

Ambari-web

Ambari-admin

[zRains]

cc @JiaLiangC

[mgucma]

Have you tried, for example: Puppeteer ?

[zRains]

Have you tried, for example: Puppeteer ?

No, just switched the test browser.

[mgucma]

Have you tried, for example: Puppeteer ?

No, just switched the test browser.

Recommended Node.js Versions:
Node.js 12.x to 16.x:

karma-chrome-launcher 3.2.0 works well with Node.js versions from 12.x to 16.x. These versions are also commonly supported by many other dependencies in the JavaScript ecosystem.

[zRains]

@mgucma Good idea, this is already in the planning stage, but it is currently limited by dependencies in the project, such as brunch. It will still take some time to handle compatibility issues.

[mgucma]

@mgucma Good idea, this is already in the planning stage, but it is currently limited by dependencies in the project, such as brunch. It will still take some time to handle compatibility issues.

@zRains Yes I know about it, I make rpm ambari under rocky 9 on docker. Without tests rpm is created. When I run tests it doesn't work and I can't find the reason.

[zRains]

@mgucma Try running the test command in the same environment without using Docker; you should be able to get error messages, or use the -X parameter.

[mgucma]

@mgucma Try running the test command in the same environment without using Docker; you should be able to get error messages, or use the -X parameter.

@zRains
The biggest problem with tests for ambari server and I had to update junit to version 4.12.3. And now I am in the process of correcting tests.

My Pull Requet to Rocky 9 will not pass, but I need Ambari update for this system. I need to do migration from Centos 7 to Rocky 9.

Can you show me the way to make corrections?

[JiaLiangC]

@mgucma

1. Ambari itself is a Java and Python program, theoretically supporting all operating systems. However, Ambari includes two acceleration libraries (.c) in the Ambari agent, which leads to coupling with the operating system.

2. The big data components managed by Ambari have different levels of coupling with the operating system, depending on their implementation. So if you want Ambari to support Rocky 9, you can refer to this PR for Rocky 8:
   https://github.com/apache/ambari/pull/3758/files

3. Because of this PR, I modified the Jenkinsfile, which will temporarily cause the project's CI/CD to fail, but this will be fixed quickly. So if you submit a PR, don't worry about the CI/CD issues caused by this PR.

The support for other big data components on Rocky 9 is controlled by the Apache Bigtop project. Additionally, I recommend that you first submit your code as a PR, so that some initial review and suggestions can be made.

[JiaLiangC]

LGTM

[JiaLiangC]

Thanks for your great work!