when subscriber can not get argo pod logs, make pod log message intuitive

[kwx4957]

Proposed changes

Fix: #4532

When subscriber pods fail to get from workflow pod or CRD, the imported logs always return the same value. This is not intuitive for users.

So, by getting the phase state from the chaos experiment run, make the log message different for each experiment phase.

But the problem remains. I'm not sure which is the best way to write the logs.

	switch phase {
	case "Completed":
		return "Experiment pod was deleted."
	case "Stopped":
		return "Experiment is stopped."
	case "Running":
		return "Experiment pod is initializing."
	case "Queue":
		return "Queue."
	case "NA":
		return "NA."
	case "Terminated":
		return "Terminated."
	case "Completed_With_Error":
		return "Completed_With_Error."
	case "Timeout":
		return "Timeout."
	case "Error":
		return "Experiment could not start."
	default:
		return "Experiment pod is initializing."
	}

• completed

- stopped

• Running

when workflow pod isn't ready	workflow pod is ready, log is changed

[namkyu1999]

Can you show us result screenshots? @kwx4957

[kwx4957]

yes i will add it

[Saranya-jena]

There can be a situation where users haven't added the cleanup chaos step, in that case, the experiment resources won't be deleted. We have to handle that situation as well

[kwx4957]

@Saranya-jena I think this function will not work in that case, because it will get data from mongoDB when getting the pod logs fails, but I will test it for that case.

[kwx4957]

@Saranya-jena I remove the podGC field and the cleanup chaos step. Is this the correct procedure? The pod logs are returning as expected