-
Task
-
Resolution: Unresolved
-
Critical
-
3.25.0.GA
-
False
-
-
False
-
-
SmokeTest is failing with Container postgresql has state CrashLoopBackOff.
Root cause:
In the https://github.com/crw-qe/quarkus-api-example-public/blob/main/devfile.yaml#L34 we are using quay.io/centos7/postgresql-13-centos7, which is not IBM Z and Power supported.
# podman pull quay.io/centos7/postgresql-13-centos7@sha256:994f5c622e2913bda1c4a7fa3b0c7e7f75e7caa3ac66ff1ed70ccfe65c40dd75 Trying to pull quay.io/centos7/postgresql-13-centos7@sha256:994f5c622e2913bda1c4a7fa3b0c7e7f75e7caa3ac66ff1ed70ccfe65c40dd75... Getting image source signatures Copying blob 1635f263c796 done | Copying blob c61d16cfe03e done | Copying blob e95916d00f10 done | Copying config a774bfb3cf done | Writing manifest to image destination WARNING: image platform (linux/amd64) does not match the expected platform (linux/ppc64le) a774bfb3cfd420f3c33c821807f3bddcf93240987972ce560eddb6f1c3c61f45ntos7"
However, while WS is starting, we can see image pulling success, and the container creation is failing
Possible solution:
find postgresql-13 container image which supports IBM Z and Power, and update https://github.com/crw-qe/quarkus-api-example-public/blob/main/devfile.yaml#L34
