Replies: 5 comments 16 replies
-
|
Changelog cannot be built, unfortunately, as we've switched from the fork to upstream MCO and this confuses release-controller. |
Beta Was this translation helpful? Give feedback.
-
No, it should be F35 (testing atm, until openshift/installer#5680 and its cherrypick to 4.10 lands). Current stable should work fine as well. |
Beta Was this translation helpful? Give feedback.
-
|
I asked because "openshift-install coreos print-stream-json" still yielded 34.20210626.3.1 |
Beta Was this translation helpful? Give feedback.
-
|
Works as expected here: |
Beta Was this translation helpful? Give feedback.
-
|
The bug is in your announcement and I didn't really read the full strings ... :-/ |
Beta Was this translation helpful? Give feedback.
-
|
Ah, my fault, sorry - rushed too much with the copypaste :/ |
Beta Was this translation helpful? Give feedback.
-
|
Upgrade from 4.9 to 4.10 failed on AWS (upgrade is hung with few nodes upgraded and few not) |
Beta Was this translation helpful? Give feedback.
-
|
Please file bugs for both cases with must-gathers |
Beta Was this translation helpful? Give feedback.
-
|
Sorry, but have no logs anymore - can't provide with the updates (I realize that it doesn't help you to find any issues). Myabe someone else who encounters the same issue will provide with the logs |
Beta Was this translation helpful? Give feedback.
-
|
I did a first fresh deployment of 4.10 on vSphere UPI and it worked. |
Beta Was this translation helpful? Give feedback.
-
|
(Meanwhile we discussed the DNS problem ... I'll have to dig deeper or reinstall later.) |
Beta Was this translation helpful? Give feedback.
-
|
Upgraded to 4.10.0-0.okd-2022-03-07-131213 from 4.9.0-0.okd-2022-02-12-140851 two clusters. Works. They repeats each minute. |
Beta Was this translation helpful? Give feedback.
-
|
That looks like MCO bug, it certainly should not hot-loop applying RBACs. Since we now use MCO from OCP please file a bugzilla for OCP (component - machine-config-operator) with must-gather attached |
Beta Was this translation helpful? Give feedback.
-
|
https://bugzilla.redhat.com/show_bug.cgi?id=2063022 |
Beta Was this translation helpful? Give feedback.
-
|
We are running OKD on bare metal and, while I was able to upgrade our cluster from 4.9.0-0.okd-2022-02-12-140851 to 4.10.0-0.okd-2022-03-07-131213, a fresh install of 4.10.0-0.okd-2022-03-07-131213 does not appear to work. The installation is stuck on the bootstrap which is apparently not able to complete its install. |
Beta Was this translation helpful? Give feedback.
-
Please attach log bundle |
Beta Was this translation helpful? Give feedback.
-
|
Hi Vadim, Here is the log bundle. Thanks. |
Beta Was this translation helpful? Give feedback.
-
|
You're starting from FCOS 34.20210626.3.2, but F35 is recommended. See https://github.com/openshift/okd/blob/master/FAQ.md#which-fedora-coreos-should-i-use. No master data collected. MCS says these never requested master Ignition - LB misconfiguration perhaps? |
Beta Was this translation helpful? Give feedback.
-
|
Hi Vadim, Indeed I found some configuration issues in my installation and after correction I was able to complete the installation. |
Beta Was this translation helpful? Give feedback.
-
|
i did successfully with fresh cluster 4.10. its worked very well |
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.10.0-0.okd-2022-03-07-131213.
Beta Was this translation helpful? Give feedback.
All reactions