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
Get OCP nodes status sometimes fails during installation, because of this internal timeout:
Error from server (Timeout): the server was unable to return a response in the time allotted,
but may still be processing the request (get nodes)
The 'get nodes status' function should be improved. Right now the playbook stop on such error.
E.g. A retry would be a better solution to handle such situation.
Here the reported error:
...
TASK [approve_certs : Cancel async 'approve_certs_task', if exists] ************
skipping: [bastion]
TASK [approve_certs : Approve all pending CSRs in the next 30 min (async task)] ***
changed: [bastion]
TASK [check_nodes : Get and print nodes status] ********************************
included: /home/jenkins/workspace/OCP-BOE/BOE-Installs/dev/ocp-multiarch-install-with-aop-ocp3_dhcp-cluster/aop/roles/common/tasks/print_ocp_node_status.yaml for bastion
TASK [check_nodes : Get OCP nodes status] **************************************
fatal: [bastion]: FAILED! => {"changed": false, "cmd": "set -o pipefail\noc get nodes -o wide | awk -F ' +' '{ printf \"%-24s %-26s %-22s %-7s %-17s %-29s %-15s\\n\", $1, $2, $3, $4, $5, $9, $6 }'\n", "delta": "0:01:00.104890", "end": "2023-08-01 08:58:51.394272", "msg": "non-zero return code", "rc": 1, "start": "2023-08-01 08:57:51.289382", "stderr": "Error from server (Timeout): the server was unable to return a response in the time allotted, but may still be processing the request (get nodes)", "stderr_lines": ["Error from server (Timeout): the server was unable to return a response in the time allotted, but may still be processing the request (get nodes)"], "stdout": "", "stdout_lines": []}
PLAY RECAP *********************************************************************
127.0.0.1 : ok=33 changed=10 unreachable=0 failed=0 skipped=32 rescued=0 ignored=0
a3elp37 : ok=7 changed=1 unreachable=0 failed=0 skipped=20 rescued=0 ignored=0
bastion : ok=73 changed=54 unreachable=0 failed=1 skipped=41 rescued=0 ignored=3
xkvmocp05 : ok=25 changed=12 unreachable=0 failed=0 skipped=24 rescued=0 ignored=0
The text was updated successfully, but these errors were encountered:
Get OCP nodes status sometimes fails during installation, because of this internal timeout:
The 'get nodes status' function should be improved. Right now the playbook stop on such error.
E.g. A retry would be a better solution to handle such situation.
Here the reported error:
The text was updated successfully, but these errors were encountered: