[OKD-SCOS v4.16] Upgrade from 4.15.0-0.okd-scos-2024-01-18-223523 to 4.16.0-0.okd-scos-2024-07-11-155249 fails: invalid config #1971
Replies: 11 comments 39 replies
-
|
There is acceptable version of 4.16.0-0.okd-scos-2024-07-21-033952 , you can check it, but I thing that you will get the same error, because the difference between 4.15.0-0.okd-scos-2024-01-18-223523 are too many! |
Beta Was this translation helpful? Give feedback.
-
|
Hi all, Can you help test this procedure on your platforms? I tested the same path of this thread's title (4.15.0-0.okd-scos-2024-01-18-223523 -> 4.16.0-0.okd-scos-2024-07-11-155249) in a fresh 4.15 OKD on AWS, and it went fine.
|
Beta Was this translation helpful? Give feedback.
-
|
Beta Was this translation helpful? Give feedback.
-
|
So it's a success Will this fix be included in the next "Accepted" or "Stable" version for SCOS 4.16/4.17? Or the next stable v4.15 SCOS version? |
Beta Was this translation helpful? Give feedback.
-
|
Has anyone gotten this guide to work on a single node cluster? After editing the kube-apiserver-operator, the actual kube-apiservers don't seem to update/pull in a new version. Re-scaling the cv operator leads to the same failure as before 😢 |
Beta Was this translation helpful? Give feedback.
-
|
@michael-willingham if you re-read my initial post and the various comments, you'll see that I've done it on a single node cluster (aka SNO) |
Beta Was this translation helpful? Give feedback.
-
|
Update from "stable" v4.15.0-0.okd-scos-2024-01-18-223523 to "next" v4.16.0-0.okd-scos-2024-07-29-184808 gives the same error ("'Could not update customresourcedefinition "infrastructures.config.openshift.io") |
Beta Was this translation helpful? Give feedback.
-
|
I've upgraded to "next" 4.16.0-0.okd-scos-2024-08-01-132038 from stable 4.15.0-0.okd-scos-2024-01-18-223523 with the same procedure. I think it cannot be applied the openshift-kube-apiserver-operator config upgrade without going through all the steps of manual reconfiguration described from @aleskandro . |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
-
|
The fixes proposed here were not working for me |
Beta Was this translation helpful? Give feedback.
-
|
Got the version 4.15 from upstream:
https://amd64.origin.releases.ci.openshift.org/graph
JOECHONG0420 ***@***.***> escreveu (quinta, 11/09/2025 à(s)
10:49):
… default upstream of the graph?
—
Reply to this email directly, view it on GitHub
<#1971 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/BXGBEW76J7YIBCEWPJJ2M2T3SFAT7AVCNFSM6AAAAACFOQTJJOVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTIMZXGIZTSMA>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
Beta Was this translation helpful? Give feedback.

Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
(this is in relation to discussion #1960)
Context
Trying to upgrade a SNO (Single Node) v4.15.0-0.okd-scos-2024-01-18-223523 cluster to v4.16.0-0.okd-scos-2024-07-11-155249
I also have tried for a multi-node cluster, it fails the same way
I've encountered the exact same problem in many other scenarios and many different versions (upgrade from OKD-FCOS v4.15 to OKD-SCOS v4.16, from OKD-FCOS v4.15 to OKD-SCOS v4.17..)
Summary
It fails with the following error:
And in cluster-version-operator logs:
So it tries to validate some
vsphereparameter while this is a baremetal UPI install ????Details
Base cluster information:
Force upgrade to v4.16.0-0.okd-scos-2024-07-11-155249
After a few minutes, the upgrade fails:
infrastructures.config.openshift.io:
[UPDATED]
After some investigation, the
openshift-cluster-version/cluster-version-operatorpod logs reports related errorsSo it seems it is trying to validate some
vsphereparameter while this is a baremetal UPI install ????Beta Was this translation helpful? Give feedback.
All reactions