search

ibm-cloud-docs / openshift

openshift prod
5 stars 41 forks source link

Incorrect instructions for adding private registry to global pull secret for VPC Gen2 clusters #152

Closed timroster closed 1 year ago

timroster commented 1 year ago

In the section Adding a private registry to the global pull secret - after applying the change to the cluster, in step 6 a command example is given to reload the workers for the updates to be applied. Using the command as provided results in this error:

ibmcloud oc worker reload -c tor-odfperf -w kube-cl3qr6gw0i4t63oc5t70-torodfperf-default-00000190
Reload worker? [kube-cl3qr6gw0i4t63oc5t70-torodfperf-default-00000190] [y/N]> y
Reloading workers for cluster tor-odfperf...
Processing kube-cl3qr6gw0i4t63oc5t70-torodfperf-default-00000190...
FAILED
Processing failed for kube-cl3qr6gw0i4t63oc5t70-torodfperf-default-00000190.

FAILED
VPC cluster worker nodes cannot be reloaded. Instead, delete the worker node and then rebalance the worker pool by using the 'worker replace' operation. (E4d01)

Incident ID: 7d1f696a-5274-4c74-abf3-bea767ccacdc
daniel-p-miller commented 1 year ago

Hi @timroster This will be fixed in our next prod push. Thanks!