"skip node" option in a nested job chain should work

Current Situation

• We assume that we have a nested job chain, i.e. a job chain with other job chains in its nodes

  <job_chain  orders_recoverable="yes" visible="yes">
      <job_chain_node.job_chain  job_chain="job_chain1" next_state="200" error_state="error" state="100"/>
      <job_chain_node.job_chain  job_chain="job_chain2" next_state="success" error_state="error" state="200"/>
      <job_chain_node.end  state="success"/>
      <job_chain_node.end  state="error"/>
  </job_chain>
  

• The first node will be skipped for example.
  • The JobScheduler returns an <ok/> after the command

    <job_chain_node.modify action='next_state' state="100" job_chain="..."/>

  • Afterwards a <show_job_chain job_chain='...'/> returns the attribute action="next_state" on the corresponding node.

    ...
             <job_chain_node action="next_state"
                             error_state="error"
                             job_chain="/test/job_chain1"
                             next_state="200"
                             state="100"/>
    ...
    

• So far so good but an added order...
  • goes to the first node of the first inner job chain job_chain1.
  • The order hangs at this node. The job at this node doesn't get a task.

Desired Behavior

• if a node of a nested job chain has the attribute action="next_state" then an order skips this node and goes to the next_state node (job_chain2 in above example).

Maintainer Notes

• This issue is not intended for immediate implementation. Analysis results in the assumption that major risks are involved with a fix to this problem.
• Please vote for this issue and let us know if this functionality meets your real-world requirements.