okd-project / okd-scos

OKD/SCOS releases
18 stars 3 forks source link

Incorrect release image in published openshift-install 4.12.0-0.okd-scos-2023-02-14-060109 #10

Closed JakobPetersson closed 1 year ago

JakobPetersson commented 1 year ago

The published artifacts for openshift-install 4.12.0-0.okd-scos-2023-02-14-060109 seems to be incorrect.

The artifacts:

Output when running the published openshift-install artifacts:

openshift-install-mac-4.12.0-0.okd-scos-2023-02-14-060109 % ./openshift-install version
./openshift-install 4.12.0-0.okd-scos-2023-02-14-060109
built from commit 3539b13d710d656867912e8497e761c507d14b6e
release image registry.ci.openshift.org/origin/release-scos@sha256:05326ac15062f909032b467b94cbcfe3540d3514b955585b782414d9e68e53a5
release architecture amd64

The release-image should (from what I can tell) be:

quay.io/okd/scos-release@sha256:968a5b06be2095ef337aaf4f5d951292875dd538b6e76d5cee826f3a6cd307d1
Goose29 commented 1 year ago

Explanation for this can be found here: https://kubernetes.slack.com/archives/C6AD6JM17/p1676973678549599

"its kinda expected. We make new releases by promoting a nightly and replacing imagestream with a quay.io ref. So installer still points to registry.ci while its just a ref to quay.io"

Workaround can be found here: https://access.redhat.com/solutions/3880221

JakobPetersson commented 1 year ago

Thank you for the quick response and info about workaround!

If this is intended, the issue can be closed.

It did not look intended since the previous release had a quay.io-url and all releases of the okd-project seem to have quay.io-urls. https://github.com/okd-project/okd