Closed alexminder closed 1 month ago
Hi,
We’ve not tested any upgrades from the older SCOS builds from January, nor do we have the ability to troubleshoot those. They were nightlies, which generally aren’t necessarily expected to interact with updates. The forced upgrade process is meant as a way to get from official 4.15 FCOS releases -> 4.16 SCOS — all of which is still just in testing. There is now official 4.16 SCOS release yet. We’ll have an update on the project in the next few days.
Thanks.
@JaimeMagiera
They were nightlies
The release was in stable channel. How can I understand where nightly release and where prod ready?
Describe the bug OKD update stuck from 4.15.0-0.okd-scos-2024-01-18-223523 to 4.16.0-0.okd-scos-2024-09-24-151747
openshift-apiserver-operator log have:
Version 4.15.0-0.okd-scos-2024-01-18-223523
How reproducible oc adm upgrade --force --allow-explicit-upgrade --to-image=quay.io/okd/scos-release:4.16.0-0.okd-scos-2024-09-24-151747
Log bundle must-gather