Replies: 6 comments 11 replies
-
|
Hey, are there no assets this time or did your pipeline break? |
Beta Was this translation helpful? Give feedback.
-
|
We still do OKD releases manually, so I forgot to attach those 🤦 Updating the release |
Beta Was this translation helpful? Give feedback.
-
|
ah okay perfect, thank you very much ;)) |
Beta Was this translation helpful? Give feedback.
-
|
@vrutkovs Is it mandatory to follow the upgrade path to use OKD 4.13? Can we directly jump from OKD 4.9-->OKD 4.13? |
Beta Was this translation helpful? Give feedback.
-
|
You must pass each step here, yes - it is possible to make workers jump from 4.9 -> 4.11 and then 4.11 -> 4.13, so workers will require just two reboots (masters will require four) |
Beta Was this translation helpful? Give feedback.
-
|
OK! Thank you! |
Beta Was this translation helpful? Give feedback.
-
|
This release not coming up as upgrade on a cluster running |
Beta Was this translation helpful? Give feedback.
-
|
I'll add upgrade edges today, stay tuned |
Beta Was this translation helpful? Give feedback.
-
|
I just got a notification for the update so the edges are live. Thanks! |
Beta Was this translation helpful? Give feedback.
-
|
Perfect, thanks! |
Beta Was this translation helpful? Give feedback.
-
|
Hi! I tried to update a fresh installed OKD cluster from 4.12.0-0.okd-2023-04-01-051724 to 4.13.0-0.okd-2023-05-22-052007 and I get this error:
Log snippet from the cluster-version-operator: I0524 17:44:46.722732 1 status.go:170] Synchronizing status errs=field.ErrorList(nil) status=&cvo.SyncWorkerStatus{Generation:5, Failure:error(nil), Done:0, Total:0, Completed:0, Reconciling:false, Initial:false, VersionHash:"", Architecture:"", LastProgress:time.Date(1, time.January, 1, 0, 0, 0, 0, time.UTC), Actual:v1.Release{Version:"4.13.0-0.okd-2023-05-22-052007", Image:"registry.ci.openshift.org/origin/release@sha256:16b7227d0c0de198d65c4478617e402d7f67ffc0dee312110a9d4c85877e5e4d", URL:"", Channels:[]string(nil)}, Verified:false, loadPayloadStatus:cvo.LoadPayloadStatus{Step:"RetrievePayload", Message:"Retrieving payload failed version="4.13.0-0.okd-2023-05-22-052007" image="registry.ci.openshift.org/origin/release@sha256:16b7227d0c0de198d65c4478617e402d7f67ffc0dee312110a9d4c85877e5e4d" failure=The update cannot be verified: unable to verify sha256:16b7227d0c0de198d65c4478617e402d7f67ffc0dee312110a9d4c85877e5e4d against keyrings: verifier-public-key-ci", AcceptedRisks:"", Failure:(*payload.UpdateError)(0xc001dc0f30), Update:v1.Update{Version:"4.13.0-0.okd-2023-05-22-052007", Image:"registry.ci.openshift.org/origin/release@sha256:16b7227d0c0de198d65c4478617e402d7f67ffc0dee312110a9d4c85877e5e4d", Force:false}, Verified:false, Local:false, LastTransitionTime:time.Time{wall:0xc113b123ab13944e, ext:511385399285, loc:(*time.Location)(0x2f4af80)}}, CapabilitiesStatus:cvo.CapabilityStatus{Status:v1.ClusterVersionCapabilitiesStatus{EnabledCapabilities:[]v1.ClusterVersionCapability(nil), KnownCapabilities:[]v1.ClusterVersionCapability(nil)}, ImplicitlyEnabledCaps:[]v1.ClusterVersionCapability(nil)}} |
Beta Was this translation helpful? Give feedback.
-
|
See #1578 - releases before Apr 10 were using expiring GPG key |
Beta Was this translation helpful? Give feedback.
-
|
neither 4.12.0-0.okd-2023-04-16-041331 :( and this page says: |
Beta Was this translation helpful? Give feedback.
-
|
|
Beta Was this translation helpful? Give feedback.
-
|
Thanks! For me it worked fine to update via CLI instead: |
Beta Was this translation helpful? Give feedback.
-
|
Hi @vrutkovs , I just tried this and I see the same high CPU issue previously found on 4.12 after deploying my agents with: Any ideas? |
Beta Was this translation helpful? Give feedback.
-
|
Hello. When trying to upgrade 4.12 to 4.13 I get error.
Tried this but does not help Tried other node without touching it, failed to, log file for that node |
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.13.0-0.okd-2023-05-22-052007.
Beta Was this translation helpful? Give feedback.
All reactions