You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When checking the version level of a cluster via the command line tool (and the IBM cloud dashboard), the tool reports the version level, even if the level is not correct due to a failed upgrade etc).
i.e. run the command;
$ ic ks cluster get -c cimf-dev
Retrieving cluster cimf-dev...
OK
Name: cimf-dev
ID: cbkdsbid0n66ecuq3vv0
State: normal
Status: All Workers Normal
Created: 2022-08-02T08:22:33+0000
Location: dal12
Pod Subnet: 172.30.0.0/16
Service Subnet: 172.21.0.0/16
Master URL: https://c106-e.us-south.containers.cloud.ibm.com:32724
Public Service Endpoint URL: https://c106-e.us-south.containers.cloud.ibm.com:32724
Private Service Endpoint URL: -
Master Location: Dallas
Master Status: Ready (3 days ago)
Master State: deployed
Master Health: normal
Ingress Subdomain: cimf-dev-9ca4d14d48413d18ce61b80811ba4308-0000.us-south.containers.appdomain.cloud
Ingress Secret: cimf-dev-9ca4d14d48413d18ce61b80811ba4308-0000
Ingress Status: healthy
Ingress Message: All Ingress components are healthy.
Workers: 3
Worker Zones: dal12
Version: 4.12.26_1562_openshift* (4.13.11_1540_openshift latest)
Creator: -
Monitoring Dashboard: -
Resource Group ID: 6c933bdaf0914f4194aa255c657a99b4
Resource Group Name: foc-cimf
OAuth Server URL: https://c106-e.us-south.containers.cloud.ibm.com:31936
Konnectivity Server URL: -
*To update to 4.13.11_1540_openshift version, run 'ibmcloud ks cluster master update --cluster cimf-dev --version 4.13.11_1540_openshift'. Review and make any required version changes before you update: 'https://ibm.biz/iks-versions'
```
The command and dashboard report the the version level of the cluster to be `4.12.26_1562_openshift`
However, looking at the OpenShift Dashboard the system reports that it's still being upgraded, and is stuck due to issues with an operator.
Thus the command line should still report that the upgrade is still ongoing, instead it reports lead to a misunderstanding and errors, as the user may then proceed to upgrade the worker nodes, or further update the admin/master nodes.
The text was updated successfully, but these errors were encountered:
When checking the version level of a cluster via the command line tool (and the IBM cloud dashboard), the tool reports the version level, even if the level is not correct due to a failed upgrade etc).
i.e. run the command;
The text was updated successfully, but these errors were encountered: