Closed jewettg closed 1 month ago
This appears to be behavior introduced in 3.50.x versions. The above "betaOptions
" error appears in both 3.50.1-2
and 3.50.2-3
.
Upon downgrading the AS3 package on my F5 to version (3.49.0-6
), the error message is no longer presented and the declaration deploys successfully.
QUESTION remains, what does "betaOptions
" mean, and why is that a valid error message?
@jewettg we introduced beta options for Per-APP-API. However Per-App API went GA is version 50.
If you GET https://10.192.75.63:443/mgmt/shared/appsvcs/settings using pre as3-50 you will see betaOptions. Post 3-50 you now see
{ "asyncTaskStorage": "data-group", "perAppDeploymentAllowed": true, "burstHandlingEnabled": false, ---- Replaced beta options. "performanceTracingEnabled": false, "performanceTracingEndpoint": "", "serializeFileUploads": false, "serviceDiscoveryEnabled": true, "webhook": "" }
@jewettg remove line 25 "bigip": "/Common/tcp" from HTTP Profile. Works fine on AS3 50.
Closing issue
Environment
Summary
I have F5 support also looking into this with case 00601595. Strange "betaOptions" error presented with no other context to indicate what the failure is, when submitting the declaration. I am using the Ansible module to deploy the declaration as follows:
Steps To Reproduce
Steps to reproduce the behavior:
Expected Behavior
Deployment of configuration to succeed.
Actual Behavior
An odd and and very non-descriptive error message "betaOptions" is presented upon declaration deployment attempt.