-
Task
-
Resolution: Done
-
Major
-
None
-
False
-
False
-
+
-
Undefined
-
We received report that it is still not possible to build the upstream Quarkus Quickstart on OCP v4.7.
How reproducible:
-----------------
1. Deploy a new OCP Cluster v4.7
2. Use Help Icon from the top right and select "Quick Starts"
3. Click on "Get started with Quarkus using s2i" quick start, Run Step 1 to 4.
4. Deployment has failed with a CrashLoopBackOff status.
Latest fix: https://github.com/quarkusio/quarkus-quickstarts/commit/dfe99e36cec416ca7a60031b53973975086e9638
(this issue re-appeared for the third time)
Reported by customer via https://bugzilla.redhat.com/show_bug.cgi?id=1938169
Lets add automated test coverage for this scenario into Quarkus OpenShift test suite so these checks get executed when we have testing cycle with RHBQ bits + when we open PR into the test suite.
Definitely not as robust as having dedicated upstream OpenShift instance and checks attached to Quarkus and Quarkus Quickstart repositories.
I hope there will be some clusters available for upstream pipelines in the foreseeable future.