-
Notifications
You must be signed in to change notification settings - Fork 344
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug]: Cassandra spark-dependencies seems to be broken #2508
Comments
Signed-off-by: Israel Blancas <[email protected]>
It seems something changed recently in the image and that is breaking the operator integration |
* Fix the CI. Change the implementation of the method to make it easy to test Signed-off-by: Israel Blancas <[email protected]> * Fix E2E Signed-off-by: Israel Blancas <[email protected]> * Disable test #2508 Signed-off-by: Israel Blancas <[email protected]> --------- Signed-off-by: Israel Blancas <[email protected]>
same issues here, we use jaeger-operator v1.49.0 last successful spark job is 20 days ago NAME COMPLETIONS DURATION AGE
jaeger-operator-jaeger-cassandra-schema-job 1/1 37s 601d
jaeger-operator-jaeger-spark-dependencies-28491835 1/1 32s 22d
jaeger-operator-jaeger-spark-dependencies-28493275 1/1 36s 21d
jaeger-operator-jaeger-spark-dependencies-28494715 1/1 37s 20d
jaeger-operator-jaeger-spark-dependencies-28523515 0/1 12h 12h operator's spark job has no tag on the image, so "latest" is used as a fallback. Containers:
jaeger-operator-jaeger-spark-dependencies:
Image: ghcr.io/jaegertracing/spark-dependencies/spark-dependencies
Port: <none>
Host Port: <none> the image that is used can be found here. https://github.com/jaegertracing/spark-dependencies/pkgs/container/spark-dependencies%2Fspark-dependencies/versions?filters%5Bversion_type%5D=tagged |
We might open an issue in that repository. |
as a workaround, we pin the spark-dependencies to the old untaggt Image sha256:683963b95bafb0721f3261a49c368c7bdce4ddcb04a23116c45068d254c5ec11 we use the Helm Values of the jaeger-operator to override the DockerImage of
However, the current image is broken and should be fixed. In my opinion, the jaeger-operator itself should also pin its own dependencies to avoid this kind of Errors in Production. |
@rriverak would you like to send a PR? |
@iblancasa I'm not sure. We can solve this on several levels... which solution are we looking for? then i cloud provide a PR accordingly.
What is our path? I would be happy if spark-dependency shows initiative here and fixes the problems with the Image and switches to a proper Versioning. If this does not happen, then one of the remaining two solutions must do the job. |
I would prefer the |
What happened?
When running the
cassandra-spark
E2E test, the pod from the spark job fails:Steps to reproduce
Run the test
Expected behavior
.
Relevant log output
No response
Screenshot
No response
Additional context
No response
Jaeger backend version
No response
SDK
No response
Pipeline
No response
Stogage backend
No response
Operating system
No response
Deployment model
No response
Deployment configs
No response
The text was updated successfully, but these errors were encountered: