search

okd-project / okd-scos

OKD/SCOS releases
26 stars 3 forks source link

4.16.0-okd-scos.1 cannot be verified against keyrings #26

Open ibotty opened 1 week ago

ibotty commented 1 week ago

When trying to update I get

Cluster version is 4.16.0-okd-scos.0

ReleaseAccepted=False

  Reason: RetrievePayload
  Message: Retrieving payload failed version="4.16.0-okd-scos.1" image="registry.ci.openshift.org/origin/release-scos@sha256:06ffff6c6951046d03df0784bc18132c368a84fe72bcfb529484a58872c3a2e1" failure=The update cannot be verified: unable to verify sha256:06ffff6c6951046d03df0784bc18132c368a84fe72bcfb529484a58872c3a2e1 against keyrings: verifier-public-key-redhat

Upstream: https://origin-release.ci.openshift.org/graph
Channel: stable-4

Recommended updates:

  VERSION           IMAGE
  4.16.0-okd-scos.1 registry.ci.openshift.org/origin/release-scos@sha256:06ffff6c6951046d03df0784bc18132c368a84fe72bcfb529484a58872c3a2e1

This cluster used to be a FCOS based OKD.

f5-jay commented 6 days ago

I'm observing the same error.

madpearl commented 5 days ago

Hi, just do:

 oc adm upgrade --clear
 ## Wait till upgrade is canceled
 ## run 
 oc adm upgrade --to-image=quay.io/okd/scos-release:4.16.0-okd-scos.1 --force --allow-explicit-upgrade
BeardOverflow commented 2 days ago

It is a common error due to signed payload key used when you are mixing nightly/rc/ec/ga releases. Go to page 2 here https://mirror.openshift.com/pub/openshift-v4/OpenShift_Release_Types.pdf