-
Notifications
You must be signed in to change notification settings - Fork 232
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
X-F5-Auth-Token has expired on versions greater than 1.13.0 #2410
Comments
Hi @jtudini91 I tested with version 1.28 without any issue on BIG-IP version 16.1 and 17.1. |
Hello @pgouband, So this issue seems to be on devices with a larger configuration. It seems that paging functionality added from v13 -> 14 causes the issues. I see that the data_increment parameter was added in. Is there any recommended value settings for the size of the configuration or hardware? |
Hi @jtudini91, This setting is useful for setups with large configurations which may take a long time with the default values. |
Hey @pgouband, I've been working with @jtudini91 on this issue. It appears this this issue results from our large configuration due to the stats for each virtual server being pulled during the gathering of the gtm-servers. The API endpoint With our large configuration, there are a large number of virtual servers that are having their Is it possible to have stats and the server configuration separated out so that only the gtm-server configuration is pulled when gtm-servers is requested? This would greatly improve the speed of the module and prevent the Auth Timeout issue that we have been experiencing. |
Hi @jtudini91, We are still reviewing it. |
COMPONENT NAME
f5networks.f5_modules.bigip_device_info
Environment
Dev/QA/Prod
ANSIBLE VERSION
BIGIP VERSION
CONFIGURATION
N/A
OS / ENVIRONMENT
N/A
SUMMARY
Trying to run any module on 1.14.0 or higher results in the following error
fatal: [bigip.example.com -> localhost]: FAILED! => {"changed": false, "msg": "b'{"code":401,"message":"X-F5-Auth-Token has expired.","referer":"10.x.x.x","restOperationId":14981760,"kind":":resterrorresponse"}'"}
STEPS TO REPRODUCE
Running the playbook to collect the device info
EXPECTED RESULTS
I expect to see output with virtual servers
ACTUAL RESULTS
The text was updated successfully, but these errors were encountered: