Skip to content
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

Kubernetes use-cases are not working #433

Closed
rsvoboda opened this issue Mar 15, 2022 · 4 comments · Fixed by #1174
Closed

Kubernetes use-cases are not working #433

rsvoboda opened this issue Mar 15, 2022 · 4 comments · Fixed by #1174
Assignees
Labels
enhancement New feature or request priority/moderate higher priority than low but lower then high

Comments

@rsvoboda
Copy link
Member

rsvoboda commented Mar 15, 2022

Kubernetes use-cases are not working, daily runs are red - https://github.com/quarkus-qe/quarkus-test-framework/actions. They fail on Kubernetes runs.

I was able to verify the same using quarkus-test-framework/examples/greetings example - OpenShift scenario works, but Kubernetes one doesn't.

cd examples/greetings
mvn clean verify -Dexclude.kubernetes.tests=no -Dts.container.registry-url=quay.io/quarkusqeteam  -Dit.test=KubernetesRemoteDevGreetingResourceIT

gives

...
16:07:56,980 INFO  kubectl: deployment.apps/app scaled
16:08:09,365 INFO  [app] [app-65887884df-m2kvc] exec java -Dquarkus.http.host=0.0.0.0 -Djava.util.logging.manager=org.jboss.logmanager.LogManager -XX:+ExitOnOutOfMemoryError -cp . -jar /deployments/quarkus-run.jar
16:08:09,366 INFO  [app] Press [h] for more options>
16:08:09,366 INFO  [app] __  ____  __  _____   ___  __ ____  ______
16:08:09,366 INFO  [app]  --/ __ \/ / / / _ | / _ \/ //_/ / / / __/
16:08:09,366 INFO  [app]  -/ /_/ / /_/ / __ |/ , _/ ,< / /_/ /\ \
16:08:09,366 INFO  [app] --\___\_\____/_/ |_/_/|_/_/|_|\____/___/
16:08:09,366 INFO  [app] 16:08:08,968 examples-greetings 1.1.0-SNAPSHOT on JVM (powered by Quarkus 2.7.4.Final) started in 2.510s. Listening on: http://0.0.0.0:8080
16:08:09,367 INFO  [app] 16:08:08,990 Profile dev activated. Live Coding activated.
16:08:09,367 INFO  [app] 16:08:08,990 Installed features: [cdi, resteasy-reactive, smallrye-context-propagation, vertx]
16:08:12,805 INFO  Running command: kubectl get svc app -n ts-ismsplioxh
16:08:12,956 INFO  kubectl: NAME   TYPE           CLUSTER-IP      EXTERNAL-IP   PORT(S)          AGE
16:08:12,957 INFO  kubectl: app    LoadBalancer   172.30.183.43   <pending>     8080:31827/TCP   16s
16:08:14,030 INFO  Running command: kubectl get svc app -n ts-ismsplioxh
16:08:14,113 INFO  kubectl: NAME   TYPE           CLUSTER-IP      EXTERNAL-IP   PORT(S)          AGE
16:08:14,114 INFO  kubectl: app    LoadBalancer   172.30.183.43   <pending>     8080:31827/TCP   18s
16:08:14,124 INFO  Running command: kubectl delete namespace ts-ismsplioxh
16:08:14,219 INFO  kubectl: namespace "ts-ismsplioxh" deleted
16:09:36,686 INFO  Running command: kubectl get svc app -n ts-ismsplioxh
16:09:36,798 INFO  kubectl: Error from server (NotFound): namespaces "ts-ismsplioxh" not found
[ERROR] Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 169.66 s <<< FAILURE! - in io.quarkus.qe.KubernetesRemoteDevGreetingResourceIT
[ERROR] io.quarkus.qe.KubernetesRemoteDevGreetingResourceIT  Time elapsed: 169.656 s  <<< FAILURE!

These two lines are suspicious:

16:08:14,124 INFO  Running command: kubectl delete namespace ts-ismsplioxh
16:09:36,686 INFO  Running command: kubectl get svc app -n ts-ismsplioxh

The namespace gets deleted but then details for app in that namespace are fetched

Running mvn clean verify -Dit.test=OpenShiftReactiveGreetingResourceIT works fine

@rsvoboda
Copy link
Member Author

rsvoboda commented Mar 15, 2022

Started happening week ago https://github.com/quarkus-qe/quarkus-test-framework/actions/runs/1960175778

But not sure what is the trigger for failures, nothing obvious in commit history

rsvoboda added a commit to rsvoboda/quarkus-test-framework that referenced this issue Mar 15, 2022
@pjgg pjgg added enhancement New feature or request priority/urgent highest priority labels Aug 3, 2022
@rsvoboda rsvoboda added priority/low lowest priority priority/moderate higher priority than low but lower then high and removed priority/urgent highest priority priority/low lowest priority labels Apr 13, 2023
@rsvoboda
Copy link
Member Author

Moving to moderate as the is no product push for it atm

@jedla97
Copy link
Member

jedla97 commented Feb 22, 2024

In recent cleanup of quay.io/quarkusqeteam there were removed these image repository:

app
pingpong
io.quarkus.qe.kubernetesremotedevmodegreetingresourceit.app
io.quarkus.qe.kubernetesusingcontainerregistrypingpongresourceit.app
io.quarkus.qe.kubernetespingpongresourceit.pingpong
io.quarkus.qe.kubernetesgreetingresourceit.app
io.quarkus.qe.kubernetessecurityresourceit.app
io.quarkus.qe.kubernetesnestedusingclientsit.app
io.quarkus.qe.kubernetesusingclientsit.app
io.quarkus.qe.kubernetespingpongresourceit.app
io.quarkus.qe.kubernetesreactivegreetingresourceit.app
io.quarkus.qe.kubernetesremotedevgreetingresourceit.app
io.quarkus.qe.books.kubernetesbasicinfinispanbookcacheit.app
io.quarkus.qe.books.kubernetesusingjksinfinispanbookcacheit.app
io-quarkus-qe-kubernetesusingextensionpingpongresourceit-app
io.quarkus.qe.kubernetesgreetingresourceit.blocking
io.quarkus.qe.kubernetesgreetingresourceit.reactive

probably to resolve this issue some of these will need to be recreated. But as they are not used atm for long periode of time they were deleted.

@gtroitsk
Copy link
Member

FW was updated to support running Kubernetes tests: #1083

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request priority/moderate higher priority than low but lower then high
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants