Gary, I ran some preliminary 72 hour tests and found that after a about 5 to 10 hours that policy locked the control loop when the packte generater cron was running in parallel with the vfwclosedloop tag.
Basically Policy would see to many requests and would lock the control loop and since we never abated the problem it would never timeout and remove the lock. I tested this morning and simply waiting long enough at steams=5 allows processing to start again for that loop. I think the root cause is the return status from APPC isnt being set so we need to wait for the 300 second timeout on the loop but the vPNG cron job doesnt have an abatement period. I think if we turn off the packet generator cron job that sets the flows from 10 to 1 etc and use the new vfwclosedloop testsuite in robot just merged that resets the streams to 5 at the end of the test even on a failure we will get a better test on the 72 hour stability. Brian -=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#17382): https://lists.onap.org/g/onap-discuss/message/17382 Mute This Topic: https://lists.onap.org/mt/31911441/21656 Group Owner: [email protected] Unsubscribe: https://lists.onap.org/g/onap-discuss/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
