Nearly every time I deploy my Quarkus application to an OpenShift cluster using the OpenShift extension, I get the following error on the OpenShift side for my first attempt:
Receiving source from STDIN as archive ...
Pulling image "quay.io/quarkus/ubi-quarkus-native-binary-s2i@sha256:d9a59f5d84de0d01a10aa77a0f3ef03533e2651a496854bfbaf86797d7694577" ...
pulling image error : manifest for quay.io/quarkus/ubi-quarkus-native-binary-s2i@sha256:d9a59f5d84de0d01a10aa77a0f3ef03533e2651a496854bfbaf86797d7694577 not found
error: build error: unable to get quay.io/quarkus/ubi-quarkus-native-binary-s2i@sha256:d9a59f5d84de0d01a10aa77a0f3ef03533e2651a496854bfbaf86797d7694577
The second attempt succeeds with:
Receiving source from STDIN as archive ...
Pulling image "quay.io/quarkus/ubi-quarkus-native-binary-s2i@sha256:2d00427fc97d217a279e54d610c2e35da5a2c1ec9c410dce41e5203f35a05281" ...
Using quay.io/quarkus/ubi-quarkus-native-binary-s2i@sha256:2d00427fc97d217a279e54d610c2e35da5a2c1ec9c410dce41e5203f35a05281 as the s2i builder image
As you can see, the hash is not the same. As the Quarkus images are rebuilt often, and I don't deploy that often, maybe that could explain things.
Nearly every time I deploy my Quarkus application to an OpenShift cluster using the OpenShift extension, I get the following error on the OpenShift side for my first attempt:
The second attempt succeeds with:
As you can see, the hash is not the same. As the Quarkus images are rebuilt often, and I don't deploy that often, maybe that could explain things.
I deploy my application with:
and I use the
quarkus-openshift
extension.Another issue slightly related, I have absolutely no feedback of the error: the Maven build is green:
The error is only visible in the OpenShift UI.
@iocanel this is the issue we discussed on Zulip the other day. You wanted a GH issue, here we go :).
https://github.com/quarkusio/quarkus/issues/15415
$upstream:15415$