Closed falc83 closed 3 months ago
Hi,
We are not working on FCOS builds of OKD any more. Please see these documents...
https://okd.io/blog/2024/06/01/okd-future-statement https://okd.io/blog/2024/07/30/okd-pre-release-testing
In terms of clusters that are older, you may be able to get help from community members. I'll convert this to a discussion to facilitate that.
Many thanks,
Jaime
Describe the bug
Update (restricted network/offline) 4.14->4.15.0-0.okd-2024-03-10-010116 was launched. The update reached the control plane stage. After the master restarted, he had the status notshedulable (for 2 hours and more) and when I tried connecting via ssh I saw an error:
"System is booting up. Unprivileged users are not permitted to log in yet. Please come back later.
After unsuccessful attempts to continue the update, there was an attempt to update to a newer version. But by mistake the old version 4.14.0-0.okd-2024-01-26-175629 was set. A rollback to the previous version occurred. All operators, masters, workers rolled back to version 4.14.0-0.okd-2024-01-26-175629. But a problem occurred in clusterversion/version. As I can understand, information that the update is complete cannot be written there. When trying to make any changes:
clusterversion still contains compatibility from version 4.15, which were not in version 4.14:
OperatorLifecycleManager, CloudCredential
It is not possible to delete them from there.Version
4.14.0-0.okd-2024-01-26-175629 4.15.0-0.okd-2024-03-10-010116
How to reproduce
oc adm upgrade --allow-explicit-upgrade --to-image ${LOCAL_REGISTRY}/${LOCAL_REPOSITORY}:4.15.0-0.okd-2024-03-10-010116 --force
oc adm upgrade --allow-explicit-upgrade --to-image ${LOCAL_REGISTRY}/${LOCAL_REPOSITORY}:4.14.0-0.okd-2024-01-26-175629 --force