Removing an Agent Cluster from a job chain is not considered

Current Situation

An Agent cluster is assigned to a job chain. The agent is not running. An order will be added to the job chain. Then the order will "wait for the agent".

Now removing the assignment of the Agent Cluster from the job chain. Then delete the order. When now a new order is added to the job chain, the order will wait for a task and the status is waiting for agent.

After changing the job configuration file of the step where the order is waiting, the order will be executed.

Desired Behavior

When removing the assignment of an Agent Cluster from a job chain this should be considered without the need to change any other configuration files.

Known Issue

• This behavior is due to the fact that the initial order that was added when the job chain was assigned an unreachable Agent was causing a task to be started. Removing the order does not remove this task that will run endlessly. If the job is configured for <job tasks="1"> then this task will prevent any further task starts.
• The required operation is therefore not just to delete the order but to kill the task. This results in the desired behavior.
• At the time of writing the JOC Cockpit Job Chains view does not display the task that is waiting for the Agent but the order only and therefore does not offer an action menu to kill the task. This situation is improved with JOC-976.