Chaos experiment fault status "RUNNING" skipped

[ParkChangSun]

What happened:

I executed a simple chaos experiment with fault 'pod-delete'. Once the status of the fault is in "INITIALIZED", it does not go to "RUNNING" status, it goes to "COMPLETED" directly.

Once subscriber get Argo Workflow changes, all nodes are updated. But subscriber is not informed the changes in ChaosEngine CR/ChaosResult CR. The phase of fault node depends on ChaosResult CR if it exists, so the phase of fault node would not be updated until the experiment is finished. ChaosResult CR is null when chaos-runner pod initialized, so the fault nodes are in "initialized" state.

What you expected to happen:

After initializing process done, it should display "RUNNING" state.

Where can this issue be corrected? (optional)

How to reproduce it (as minimally and precisely as possible):

Start a simple chaos experiment. ('pod-delete')

Anything else we need to know?:

I will take this issue.

Fault node is "Initialized" until "Completed"

When fault node completed/Argo Workflow CR changed