-
Notifications
You must be signed in to change notification settings - Fork 71
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]: New Docker-Image breaks jaeger-operator spark-dependencies-jobs #138
Comments
All previous images are still available: https://github.com/jaegertracing/spark-dependencies/pkgs/container/spark-dependencies%2Fspark-dependencies/versions Running |
Sadly, the ci.yaml does not include any tests against Cassandra, only Elasticsearch. It also doesn't log anything about containers being executed - would be nice to include |
The lack of other Tags makes it difficult to use anything other than A versioning according to SemVer would be helpful to allow Image Pinning by the Jaeger Operator. |
Previously, Spark Cassandra Connector and Spark Core was using metrics-core 3.x and 4.x respectively. Bumping Cassandra Connector integrates a newer Cassandra Java Driver, so it does not interfere with spark's metrics-core version. Fixes jaegertracing#138
Previously, Spark Cassandra Connector and Spark Core was using metrics-core 3.x and 4.x respectively. Bumping Cassandra Connector integrates a newer Cassandra Java Driver, so it does not interfere with spark's metrics-core version. Fixes jaegertracing#138 Signed-off-by: Vladimir Sitnikov <sitnikov.vladimir@gmail.com>
Previously, Spark Cassandra Connector and Spark Core was using metrics-core 3.x and 4.x respectively. Bumping Cassandra Connector integrates a newer Cassandra Java Driver, so it does not interfere with spark's metrics-core version. Fixes jaegertracing#138 Signed-off-by: Vladimir Sitnikov <sitnikov.vladimir@gmail.com>
Previously, Spark Cassandra Connector and Spark Core was using metrics-core 3.x and 4.x respectively. Bumping Cassandra Connector integrates a newer Cassandra Java Driver, so it does not interfere with spark's metrics-core version. Fixes jaegertracing#138 Signed-off-by: Vladimir Sitnikov <sitnikov.vladimir@gmail.com>
Previously, Spark Cassandra Connector and Spark Core was using metrics-core 3.x and 4.x respectively. Bumping Cassandra Connector integrates a newer Cassandra Java Driver, so it does not interfere with spark's metrics-core version. Fixes jaegertracing#138 Signed-off-by: Vladimir Sitnikov <sitnikov.vladimir@gmail.com>
Previously, Spark Cassandra Connector and Spark Core was using metrics-core 3.x and 4.x respectively. Bumping Cassandra Connector integrates a newer Cassandra Java Driver, so it does not interfere with spark's metrics-core version. Fixes jaegertracing#138 Signed-off-by: Vladimir Sitnikov <sitnikov.vladimir@gmail.com>
What happened?
Since the last update (20 days ago) of the Docker image which overwrote the 'latest' tag, the spark-job of the jaeger-operator stopped Working.
see operator issue here: jaegertracing/jaeger-operator#2508
Steps to reproduce
Use the latest version of jaeger-operator (1.49.0) and the Spark-jobs will fail.
Expected behavior
At least the old Docker-Image should be available. Overwriting the latest tag prevents any Workaround.
Relevant log output
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
Kubernetes
Deployment configs
No response
The text was updated successfully, but these errors were encountered: