Java cannot find certification path #9354
Assignees
Labels
Comments
|
Hi! Please provide a minimal project to reproduce the problem |
|
Sure, the project itself is open source, so you can clone or fork it from https://github.com/logikal-io/mindlab, that should reproduce the problem. Everything is public, including the workflows. You can run the failing test with If you need anything else, e.g. a Dockerfile with the working example, let me know. |
|
well, I'd say it is still too broad to identify the problem, from what seen we still need the following info:
|
|
Apart from that, as far as I understand the auth failure happens because of the lack of some jvm parameters such as |
|
Good questions! The application is using PySpark to read a test file from a Google Cloud Storage bucket (using gcs-connector from https://github.com/GoogleCloudDataproc/hadoop-connectors). From what I understand Python is invoking Java under the hood via Py4J (https://www.py4j.org/py4j_java_gateway.html). I don't think there's any particular options used for this invocation, or if there are, that's handled by PySpark. I generally just install Hadoop and I'm not sure if the problem is with reading from the bucket or with identity federation. I'm not setting any parameters like |
|
@GergelyKalmar could you please describe your docker local workflow (Dockerfile/build commands/commands you run in container, what docker image is used as base, etc) to compare outputs from docker and from runner then? |
|
Sure. You can use these commands in a Dockerfile: Then you can run the image and the tests as follows: Note that you need to have the gcloud CLI installed and the application default credentials needs to be available on your local machine too (see https://cloud.google.com/docs/authentication/provide-credentials-adc#google-idp). The test reads a CSV file from a public bucket, so there should be no access problems. |
|
If there is anything I can do to get some more information about the error (e.g. some Java logs) please let me know! I tried setting |
|
Changed the logs from the executors to the driver, that worked, there are some debug-level logs now (see https://github.com/logikal-io/mindlab/actions/runs/7940823201/job/21682513603). Here is what I see when running locally: And here are the logs when running in GitHub Actions: |
|
Hey @GergelyKalmar, I also tried invoking Dockerfile commands directly on a runner with results similar to above. |
|
Hi @shamil-mubarakshin, thank you very much for trying it out! You are right, the object wasn't public. I changed the access so it should be publicly readable now, can you try again? |
|
Direct invocation of Dockerfile commands succeeded. Those issues doesn't seem image related so far. Since now public access was enabled, could you re-run your workflow for |
|
Okay, very interesting. Indeed the failed tests are not the ones that I am running into, these can be ignored. I had re-run the tests, however, they are still failing with the same error. It is wild, looks like the jobs are almost exactly the same. One difference I see is that my job is using workload identity federation with |
|
Opened a ticket in the meantime with the Google auth action, perhaps they have an idea what is happening. Nonetheless it would be great if this could be still reproduced with the GitHub Actions runner. |
|
@GergelyKalmar, using |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
We're seeing the following error when running our test suite in GitHub Actions:
The test suite runs fine locally on an Ubuntu 20.04 LTS desktop environment, it also runs fine inside a clean Ubuntu base image from Docker.
Platforms affected
Runner images affected
Image version and build link
See https://github.com/logikal-io/mindlab/actions/runs/7835150901/job/21629489569
Is it regression?
Probably not
Expected behavior
We expect our tests to succeed.
Actual behavior
The tests fail.
Repro steps
Run the test suite in the given repository in GitHub Actions.
Note that the issue has also been reported at GoogleCloudDataproc/hadoop-connectors#1106, but as it only appears on GitHub Actions and not when running locally or on a clean Ubuntu image, we think it might be related to the GitHub Actions image.
The text was updated successfully, but these errors were encountered: