Replies: 5 comments 14 replies
-
|
OKD releases have been updated to use new GPG key (previous one will expire at the end of the month). |
Beta Was this translation helpful? Give feedback.
-
|
I get the error now: What might be the problem? |
Beta Was this translation helpful? Give feedback.
-
|
Setting this as admin helps ;-): |
Beta Was this translation helpful? Give feedback.
-
|
I know and did, but this was before the previous key expired. |
Beta Was this translation helpful? Give feedback.
-
|
|
Beta Was this translation helpful? Give feedback.
-
|
I'm having issues creating new clusters with this version of the OKD installer. Last week it worked flawlessly and now the bootstrap is incapable of downloading the release-image: I've tried to locally download it using docker and it fails as this checksum no longer exists in the quay.io registry: The registry is accessible as I can download the most recent one tagged in the releas 4.13:
Is it the expected behaviour to modify previous images on each release? This means invalidating the previous OKD installer releases, right? |
Beta Was this translation helpful? Give feedback.
-
|
Luckily the cluster deployments are done in a sandbox environment and I've been able to deploy it again using the latest 4.13 installer. Anyway, it's good to know that it's just an unexpected mistake, not the usual behaviour. |
Beta Was this translation helpful? Give feedback.
-
|
Re-uploaded the artifacts |
Beta Was this translation helpful? Give feedback.
-
|
Possible others are still missing, cluster-version-operator fails to pull for example |
Beta Was this translation helpful? Give feedback.
-
|
Ah, github is silly - I attached new installer archive, but since the names match it has retained it. Re-uploading again |
Beta Was this translation helpful? Give feedback.
-
I have exactly the same problem with cluster-version-operator in existing cluster, how to fix it? |
Beta Was this translation helpful? Give feedback.
-
|
@tyronewilsonfh that's precisely the artifact that had the mismatch in the SHA checksum yesterday. I see that it still points towards a different SHA. @vrutkovs could you please check it? Thanks! |
Beta Was this translation helpful? Give feedback.
-
|
Check the updated installer? Just uploaded a new one and it looks good here: |
Beta Was this translation helpful? Give feedback.
-
|
Yeah, that's what I though! Then the only thing to change is the |
Beta Was this translation helpful? Give feedback.
-
|
It seems the mac intel installer binary is missing? Now I'm getting 404 on openshift-install-mac-4.12.0-0.okd-2023-04-16-041331.tar.gz which I didn't when the release was initially. |
Beta Was this translation helpful? Give feedback.
-
|
That is gone it seems. Note that there have been two releases since 4-16-2023. You can find the installers for those versions in the usual locations. |
Beta Was this translation helpful? Give feedback.
-
|
Yes, the later 4.13 release installers works nicely, but since this is the last (?) 4.12 release, it's really good to have as reference for testing stuff that matches OCP 4.12 in the production environment. If there had been a later 4.12 release I wouldn't have cared. |
Beta Was this translation helpful? Give feedback.
-
|
hmm, not sure why the mac installer was not uploaded, uploading it now. In any case, you can extract all installers from release payload: |
Beta Was this translation helpful? Give feedback.
-
Client tools for OpenShift
These archives contain the client tooling for OpenShift.
To verify the contents of this directory, use the 'gpg' and 'shasum' tools to
ensure the archives you have downloaded match those published from this location.
The openshift-install binary has been preconfigured to install the following release:
This discussion was created from the release 4.12.0-0.okd-2023-04-16-041331.
Beta Was this translation helpful? Give feedback.
All reactions