[m@fedora containers]$ oc get clusterversion NAME VERSION AVAILABLE PROGRESSING SINCE STATUS version 4.10.0-0.nightly-2022-05-05-171206 True False 70m Cluster version is 4.10.0-0.nightly-2022-05-05-171206 [m@fedora containers]$ oc get nodes NAME STATUS ROLES AGE VERSION mgahagan411-g2sj8-master-0 Ready master 94m v1.23.5+b463d71 mgahagan411-g2sj8-master-1 Ready master 94m v1.23.5+b463d71 mgahagan411-g2sj8-master-2 Ready master 94m v1.23.5+b463d71 mgahagan411-g2sj8-worker-mtcazs-7n7wh Ready worker 85m v1.23.5+b463d71 mgahagan411-g2sj8-worker-mtcazs-nvgjp Ready worker 77m v1.23.5+b463d71 mgahagan411-g2sj8-worker-mtcazs-zk4ll Ready worker 83m v1.23.5+b463d71 az vm show -g mgahagan411-g2sj8-rg -n mgahagan411-g2sj8-master-0 "osDisk": { "caching": "None", "createOption": "FromImage", "diskSizeGb": 1023, "encryptionSettings": null, "image": null, "managedDisk": { "id": "/subscriptions/de7e09c3-b59a-4c7d-9c77-439c11b92879/resourceGroups/mgahagan411-g2sj8-rg/providers/Microsoft.Compute/disks/mgahagan411-g2sj8-master-0_OSDisk", "resourceGroup": "mgahagan411-g2sj8-rg", "storageAccountType": "Premium_LRS" }, "name": "mgahagan411-g2sj8-master-0_OSDisk", "osType": "Linux", "vhd": null, "writeAcceleratorEnabled": null } this one can verified, this is a 4.10 cluster, I just named it incorrectly
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (OpenShift Container Platform 4.10.14 bug fix update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2022:2178