-
|
So, to put it briefly, I have 3 OKD SCOS clusters on different versions, installed at different times. On none of them I have the option to upgrade via the native stable-scos-4 channel. This surprises me because I had previously upgraded one of these clusters without any issues, but after one of the upgrades, the option no longer appears. The API responsible for checking if an upgrade is available responds and returns results. When I look at the release tree, it indeed seems like there is no option to migrate to a higher version of OKD SCOS, but I wonder why? I’ve tried changing channels, but none of them were suitable. Should I change the channel? If I want to move to a higher version, do I need to reinstall the cluster from scratch? Is there any option for me to upgrade at all?
|
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 3 replies
-
|
you have to use --force and --allow-explicit-upgrade for example: |
Beta Was this translation helpful? Give feedback.
-
|
Seems kinda risky to go all out without knowledge if it's gonna work out or not. Anyways gonna try this at weekend, thanks for an idea |
Beta Was this translation helpful? Give feedback.
-
|
read this issue to get more info about jumping to the new version of stable 4.15 and then 4.16 |
Beta Was this translation helpful? Give feedback.
-
|
Worked like a charm, thanks |
Beta Was this translation helpful? Give feedback.
you have to use --force and --allow-explicit-upgrade for example:
# oc adm upgrade --to-image registry.ci.openshift.org/origin/release-scos:4.16.0-0.okd-scos-2024-09-20-093254 --force --allow-explicit-upgrade