I am working with executing scripts on a F5 BIg IP load balancer.
This is the script I execute without any issue , manually from Node->Configs->Execute Script widget ((forces a node offline, waits 2 min, then enables the node).
Behavior on the F5 shows what I would expect (changes pending, in sync, device is offline, 2 minute gap, changes pending, in sync, device online)
tmsh
modify /ltm node 10.100.55.55 state user-down session user-disabled
run /cm config-sync to-group sg-sf
${Delay:30}
show /cm sync-status
${Delay:30}
show /cm sync-status
${Delay:30}
show /cm sync-status
${Delay:30}
show /cm sync-status
modify /ltm node 10.100.55.55 state user-up session user-enabled
run /cm config-sync to-group sg-sf
----------------------------------------------------------------------------------------------
When adding this same script to an Alert as a Trigger Action ->"Execute an NCM Action" -> "Execute Config Script".
The resulting test(simulate/execute) takes more then 2 minutes and results in the "executing script" box ending with a general "error".
The F5 shows confusing behavior (changes pending, in sync, device offline, wait, changes pending, in sync, changes pending, in sync, device still offline, not all devices in sync, in sync, not all devices in sync, in sync, changes pending, device online).
Commands seem to be repeating/looping.
Any thoughts why the Alert trigger action "Execute an NCM action" would behave so inconsistently vs the Executing the script manually from the Node-> Configs->Execute Script widget?
