Repository navigation
HADOOP-19994. Start PhantomJS with OPENSSL_CONF=/dev/null for catalog webapp Jasmine tests - #8757
Merged
slfan1989 merged 1 commit intoOct 6, 2026
Conversation
|
💔 -1 overall
This message was automatically generated. |
… webapp Jasmine tests PhantomJS 2.1.1, downloaded by phantomjs-maven-plugin for the hadoop-yarn-applications-catalog-webapp Jasmine specs, bundles OpenSSL 1.x. On OpenSSL 3 systems (e.g. the Ubuntu noble precommit image) /etc/ssl/openssl.cnf declares "providers = provider_sect"; OpenSSL 1.x tries to dlopen libproviders.so, fails with "Auto configuration failed" and exits before opening its WebDriver port, so jasmine-maven-plugin times out with UnreachableBrowserException and the reactor stops. jasmine-maven-plugin and PhantomJSDriverService offer no way to set the browser's environment, so on Unix start PhantomJS through /bin/sh -c 'OPENSSL_CONF=/dev/null exec "$0" "$@"', using the phantomjs.binary.path and phantomjs.cli.args capabilities. This scopes the workaround to the PhantomJS process, the same approach as RANGER-4791, and fixes local builds on any OpenSSL 3 distro as well as CI. Windows keeps launching PhantomJS directly. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
joseluisll
force-pushed
the
HADOOP-19994-phantomjs-openssl3
branch
from
September 27, 2026 17:40
b2a3cb5 to
65b59cf
Compare
|
💔 -1 overall
This message was automatically generated. |
slfan1989
approved these changes
Oct 4, 2026
slfan1989
left a comment
slfan1989
left a comment
Contributor
There was a problem hiding this comment.
+1.
This fixes the PhantomJS startup failure observed in precommit.
The existing Java and Jasmine tests pass with the patch.
Since this only changes the test launcher configuration, the existing Jasmine suite provides appropriate validation; additional unit tests are not necessary.
This was referenced Oct 4, 2026
Merged
Contributor
Author
|
@slfan1989 thanks for the review! Would you be able to merge this when you have a moment? |
Contributor
@joseluisll Thanks for the contribution! Merged into trunk. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Required by (waits for this one to be merged):
Description of PR
JIRA: HADOOP-19994. Start PhantomJS with OPENSSL_CONF=/dev/null for catalog webapp Jasmine tests
PhantomJS 2.1.1 (downloaded by phantomjs-maven-plugin for the
hadoop-yarn-applications-catalog-webappJasmine specs) bundles OpenSSL 1.x. On OpenSSL 3 systems, such as the ubuntu-noble precommit image,/etc/ssl/openssl.cnfdeclaresproviders = provider_sect. OpenSSL 1.x fails to loadlibproviders.so, prints "Auto configuration failed" and exits before opening its WebDriver port. jasmine-maven-plugin then fails withUnreachableBrowserException, the reactor stops, and the unit vote is -1 on every PR.Fix: a Unix-only profile (
phantomjs-openssl-conf) in the catalog-webapp pom starts PhantomJS through/bin/sh -c 'OPENSSL_CONF=/dev/null exec "$0" "$@"' <phantomjs> ..., using thephantomjs.binary.pathandphantomjs.cli.argscapabilities.OPENSSL_CONFis set only for the process that starts PhantomJS. Ranger used frontend-maven-plugin'senvironmentVariables. jasmine-maven-plugin /PhantomJSDriverServicecannot set the browser's environment (it logsenvironment: {}), hence thesh -cwrapper.OPENSSL_CONFchange, which would affect every tool in the container./dev/nullis an empty, valid config on every system.How was this patch tested?
Ubuntu 24.04, OpenSSL 3.0.13 (same
openssl.cnfas the precommit image):mvn test -pl hadoop-yarn-project/hadoop-yarn/hadoop-yarn-applications/hadoop-yarn-applications-catalog/hadoop-yarn-applications-catalog-webappBefore:
Auto configuration failed
...filename(libproviders.so): libproviders.so: cannot open shared object file
...MODULE_LOAD_DSO:error loading dso:conf_mod.c:285:module=providers, path=providers
[ERROR] Failed to execute goal com.github.searls:jasmine-maven-plugin:2.1:test ... UnreachableBrowserException
BUILD FAILURE
After:
INFO: executable: /bin/sh
Results: 15 specs, 0 failures, 0 pending
BUILD SUCCESS
Checked with
help:effective-pomthat with the profile deactivated (as on Windows), the jasmine configuration is unchanged.For code changes:
LICENSE,LICENSE-binary,NOTICE-binaryfiles? (N/A)AI Tooling
Contains content generated by Claude Code.