-
Notifications
You must be signed in to change notification settings - Fork 233
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
bigip_ucs_fetch - Traceback on UCS fetch #2388
Comments
Hi @apellini, I tested the following playbook with version 16.1.3.2 without any issue so it's maybe something in your environment.
|
I have done some test with verbose:
What we could see that UCS is created because on next task remove it from device:
|
Hi @apellini, Have you tested with the playbook I provided? |
Yes. I have launched two times and has worked. We have a strange behaviour with async_timeout at 300 sec, the first time has taken 294 sec and second 632 sec. I was expecting that when 300 sec is reached task gone in failed. Also consider that we are using 1800 sec as async_timeout because it is needed from other F5. |
Hi @apellini, Async_timeout is only for ucs creation not the task. |
yes but why if I put 1800 sec doesn't work? |
Hi @apellini, I did the test with 1800 and I have no issue so it's maybe something related to your environment. |
But the strangest thing if I put 1800 it fails after 24 min not 30. TASK [Collect UCS] ************************************************************* |
Hi @apellini, Best way to go forward, will be to do a repro with your ucs configuration so you need to open a case via https://my.f5.com |
COMPONENT NAME
Environment
ANSIBLE VERSION
BIGIP VERSION
CONFIGURATION
OS / ENVIRONMENT
RHEL 7.9
SUMMARY
UCS Backup not working on some device and traceback not useful to understand the issue
STEPS TO REPRODUCE
EXPECTED RESULTS
Backup performed
ACTUAL RESULTS
The text was updated successfully, but these errors were encountered: