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
The following task in Ansible/ansible_collections/jfrog/platform/roles/xray/tasks/install.yml is not waiting long enough before failing. The Xray service was still in activating state. :
- name: Make sure xray is up and running
ansible.builtin.uri:
url: http://127.0.0.1:8082/router/api/v1/system/health
timeout: 130
status_code: 200
register: result
until: result is succeeded
retries: 25
delay: 5
when:
- not ansible_check_mode
- xray_start_service | bool
Should be at least 5 minutes or 15..
- name: Make sure xray is up and running
ansible.builtin.uri:
url: http://127.0.0.1:8082/router/api/v1/system/health
timeout: 130
status_code: 200
register: result
until: result is succeeded
retries: 30
delay: 10
when:
- not ansible_check_mode
- xray_start_service | bool
The text was updated successfully, but these errors were encountered:
Note: happens only on fresh install. Future attempts are faster.
EmptyByte
changed the title
[ansible/xray] timeout for xray API check is too short. Tasks fails but service is still activating.
[ansible/xray] timeout for xray API check is too short. Task fails but service is still activating.
Oct 28, 2024
Thanks for raising this! Do you have any insights into how many seconds it took for the fresh install to connect successfully? We're trying to understand if this issue is isolated to just one environment or if it occurs consistently across others.
Hi @chukka, I don't remember exactly but it took some time, I would say close to 5 minutes. Nonetheless, if you configure 5 minutes, this is a max and the task will finish earlier or timeout when 5 minutes were elapsed.
The following task in
Ansible/ansible_collections/jfrog/platform/roles/xray/tasks/install.yml
is not waiting long enough before failing. The Xray service was still in activating state. :Should be at least 5 minutes or 15..
The text was updated successfully, but these errors were encountered: