When stopping an octavia controller with jobboard, the Job (and the flow and tasks) is abruptly terminated. It means that the resources are left in a undefined state in the persistence DB.

Another controller have no issue for resuming the work but it may introduce some side effects:

If the terminated task creates a resource (for instance a nova VM or a port in Neutron) and is killed before saving its state, the task will be resumed on another controllre and the resource will be created again, it may lead to wasted/unattached resources.

The right approach would be to let taskflow terminate the current task gracefully (putting it in a SUSPEND state), so its state is preserved.

Bug was reported upstream in https://bugs.launchpad.net/octavia/+bug/2064101