Closed fedinskiy closed 2 years ago
/cc @Sgitario, @geoand, @iocanel
Can you share the Quarkus application logs as well?
I suspect the issue is in OpenShiftClient.isCustomResourceReady
, not in Quarkus. Perhaps, it should be reported in the Fabric8 Kubernetes Client @manusa
@Sgitario application logs for failed and successful run are here: https://gist.github.com/fedinskiy/7e9f9c6ec7ef56296c44837b2831ee28
The only meaningful difference I was able to find is difference between versions of dependencies and one new dependency:
org.eclipse.microprofile.metrics.microprofile-metrics-api-3.0.1.jar
UPD: different dependencies were added to the gist
Since the application starts ok, I dont think this is caused by those new dependencies or Quarkus, but an issue either in your Quarkus QE Testing framework (something you need to change to use the new Fabric8 Kubernetes Client) or in Fabric8 Kubernetes
I agree with @Sgitario. My guess is that something is different in Kubernetes Client 6.x (cc @manusa)
It certainly doesn't look like an error caused by a change of the microprofile-metrics-api
dependency version.
I need to clone github.com:quarkus-qe/quarkus-test-suite.git and further investigate what might be the issue. Right now I can only say that it looks like the CRD is not properly configured. We did change the behavior for non-standard/CRD APIs but I can't recall if we implemented the check to verify that a CRD existed before allowing operations on that API resource.
BTW, is this running on a real cluster or on the Mock Server? For some reason I assumed the latter, but now I realize that might not be the case.
This dependency has an unaligned version of the client.
...
+- io.quarkus.qe:quarkus-test-openshift:jar:1.2.0.Beta12:test
[INFO] | +- io.fabric8:openshift-client:jar:5.12.3:test
[INFO] | | +- io.fabric8:kubernetes-client:jar:5.12.3:test
[INFO] | | | +- io.fabric8:kubernetes-model-core:jar:5.12.3:test
[INFO] | | | +- io.fabric8:kubernetes-model-rbac:jar:5.12.3:test
[INFO] | | | +- io.fabric8:kubernetes-model-admissionregistration:jar:5.12.3:test
[INFO] | | | +- io.fabric8:kubernetes-model-apps:jar:5.12.3:test
[INFO] | | | +- io.fabric8:kubernetes-model-autoscaling:jar:5.12.3:test
[INFO] | | | +- io.fabric8:kubernetes-model-apiextensions:jar:5.12.3:test
[INFO] | | | +- io.fabric8:kubernetes-model-batch:jar:5.12.3:test
...
I'm not sure if this will fix the issue, but the quarkus-test-openshift
project needs to be updated.
Many thanks @manusa ! I'm closing this issue.
Describe the bug
I have an application, which deploys Kafka on Openshift via amq-streams operator, checks it status, connects to it via quarkus-smallrye-reactive-messaging-kafka and when deletes it. It uses fabric8 library to check status of the operator. This works flawlessly with Quarkus 2.13.0.Final, but fails when running with 999-SNAPSHOT
Expected behavior
The scenario should work without failures.
Actual behavior
The scenario fails with this stacktrace:
How to Reproduce?
git clone git@github.com:quarkus-qe/quarkus-test-suite.git
oc
binary exists on $PATHmvn clean verify -Popenshift -pl messaging/kafka-streams-reactive-messaging/ -Dall-modules -Dit.test=OperatorOpenShiftAmqStreamsKafkaStreamIT
. It should fail.mvn clean verify -Popenshift -pl messaging/kafka-streams-reactive-messaging/ -Dall-modules -Dit.test=OperatorOpenShiftAmqStreamsKafkaStreamIT -Dquarkus.platform.version=2.13.0.Final
. It should succeed.Output of
uname -a
orver
5.19.11-200.fc36.x86_64
Output of
java -version
11.0.16
GraalVM version (if different from Java)
No response
Quarkus version or git rev
6dad45448433bbe1b902d3ac3db6ea4782195197
Build tool (ie. output of
mvnw --version
orgradlew --version
)Apache Maven 3.8.6 (84538c9988a25aec085021c365c560670ad80f63)
Additional information