This is potentially a transient error caused by the api server being overloaded. "stderr": "Error from server (TooManyRequests): the server has received too many requests and has asked us to try again later (get deployments.extensions webconsole)\\n" The error in the log was due to insufficient 'until' condition handling on the previous task, "Verify that the console is running".
(In reply to Russell Teague from comment #4) > This is potentially a transient error caused by the api server being > overloaded. > > "stderr": "Error from server (TooManyRequests): the server has received too > many requests and has asked us to try again later (get > deployments.extensions webconsole)\\n" > > The error in the log was due to insufficient 'until' condition handling on > the previous task, "Verify that the console is running". The webconsole and console seem to be working properly. Is it OK to continue and proceed with the node upgrade? Thanks!
(In reply to Sam Yangsao from comment #5) > (In reply to Russell Teague from comment #4) > > This is potentially a transient error caused by the api server being > > overloaded. > > > > "stderr": "Error from server (TooManyRequests): the server has received too > > many requests and has asked us to try again later (get > > deployments.extensions webconsole)\\n" > > > > The error in the log was due to insufficient 'until' condition handling on > > the previous task, "Verify that the console is running". > > The webconsole and console seem to be working properly. Is it OK to > continue and proceed with the node upgrade? > > Thanks! Ignore this question, we'll need the control plane upgraded completely first from chatting with another team member prior to proceeding with the node upgrade. Still need some guidance on the original error and how to proceed. Thanks!
The PR referenced above was opened to better handle situations where the API server was busy causing the 'TooManyRequests' error. The upgrade is not complete because the web console is not the last item to be upgraded in the upgrade process. The upgrade could be attempted again to complete the controle plane upgrade. Prior to running the control plane upgrade, you can also verify the web console upgrade will complete by running just the web console playbook, playbooks/openshift-web-console/config.yml. Running this playbook will install/upgrade the web console to the openshift version specified in the inventory.
Just a heads up, customer re-ran the `upgrade_control_plane.yml` playbook and confirmed that the playbook completed. They are now going through the node upgrade playbook. Thanks!
Fixed. openshift-ansible-3.11.135-1.git.0.b7ad55a.el7 Upgrade success, no error.
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, 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-2019:2352