Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Get OCP nodes status sometimes fails during installation, because of an internal timeout #184

Open
smolin-de opened this issue Aug 1, 2023 · 0 comments

Comments

@smolin-de
Copy link
Contributor

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   
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant