Fix CoreDNS for litmus 1.13.8 and above

[tanmaypandey7]

What this PR does / why we need it: CoreDNS pod delete experiment fails with litmus 1.13.8

Which issue this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged): fixes # Fixes CoreDNS https://github.com/litmuschaos/litmus-ansible/issues/35 bug

Checklist

• [✅ ] Does this PR have a corresponding GitHub issue?
• [ ] Have you included relevant README for the chaoslib/experiment with details?
• [ ] Have you added debug messages where necessary?
• [ ] Have you added task comments where necessary?
• [ ] Have you tested the changes for possible failure conditions?
• [ ] Have you provided the positive & negative test logs for the litmusbook execution?
• [ ] Does the litmusbook ensure idempotency of cluster state?, i.e., is cluster restored to original state?
• [ ] Have you used non-shell/command modules for Kubernetes tasks?
• [ ] Have you (jinja) templatized custom scripts that is run by the litmusbook, if any?
• [ ] Have you (jinja) templatized Kubernetes deployment manifests used by the litmusbook, if any?
• [ ] Have you reused/created util functions instead of repeating tasks in the litmusbook?
• [ ] Do the artifacts follow the appropriate directory structure?
• [ ] Have you isolated storage (eg: OpenEBS) specific implementations, checks?
• [ ] Have you isolated platform (eg: baremetal kubeadm/openshift/aws/gcloud) specific implementations, checks?
• [ ] Are the ansible facts well defined? Is the scope explicitly set for playbook & included utils?
• [ ] Have you ensured minimum/careful usage of shell utilities (awk, grep, sed, cut, xargs etc.,)?
• [ ] Can the limtusbook be executed both from within & outside a container (configurable paths, no hardcode)?
• [ ] Can you suggest the minimal resource requirements for the litmusbook execution?
• [ ] Does the litmusbook job artifact carry comments/default options/range for the ENV tunables?
• [ ] Has the litmusbooks been linted?

Special notes for your reviewer:

[tanmaypandey7]

Working logs:

2022-05-25 12:26:03.680896 ************ BRACE YOURSELF, EXPERIMENT BEGINS! ************

2022-05-25 12:26:04.962867 Step: Gathering Facts

2022-05-25 12:26:05.968562 Step: Identify the chaos util to be invoked

2022-05-25 12:26:06.019489 Step: include_vars

2022-05-25 12:26:06.108170 Step: Construct chaos result name
included: /utils/runtime/update_chaos_result_resource.yml for 127.0.0.1

2022-05-25 12:26:06.821358 Step: [PreReq]: Generate the chaos result CR to reflect SOT (Start of Test)

2022-05-25 12:26:10.628150 Step: [PreReq]: Apply the chaos result CR for coredns-pod-delete experiment

2022-05-25 12:26:11.368598 Step: Provision nginx pod

2022-05-25 12:26:11.989078 Step: Provision liveness pod

2022-05-25 12:26:12.860420 Step: Deploying and exposing nginx pod

2022-05-25 12:26:13.832861 Step: Deploying liveness pod
included: /utils/common/status_app_pod.yml for 127.0.0.1

2022-05-25 12:26:14.881669 Step: [Status]: Checking whether application pods are in running state

2022-05-25 12:26:15.414533 Step: [Status]: Checking whether application containers are in running state
included: /utils/common/status_app_pod.yml for 127.0.0.1
FAILED - RETRYING: [Status]: Checking whether application pods are in running state (90 retries left).
FAILED - RETRYING: [Status]: Checking whether application pods are in running state (89 retries left).
FAILED - RETRYING: [Status]: Checking whether application pods are in running state (88 retries left).

2022-05-25 12:26:24.008382 Step: [Status]: Checking whether application pods are in running state

2022-05-25 12:26:24.519375 Step: [Status]: Checking whether application containers are in running state
included: /utils/common/generate-kubernetes-chaos-events.yml for 127.0.0.1

2022-05-25 12:26:24.950662 Step: [Event]: Obtain the current date in ISO8601 format

2022-05-25 12:26:25.017494 Step: set_fact

2022-05-25 12:26:26.641427 Step: [Event]: Creating a PreChaosCheck event in the chaosengine
included: /chaoslib/litmus/pod_delete/pod_failure_by_litmus.yml for 127.0.0.1

2022-05-25 12:26:26.818183 Step: [Prepare]: Deriving the chaos iterations

2022-05-25 12:26:27.380743 Step: [Prepare]: Generate a run id if not passed from the engine/experiment

2022-05-25 12:26:27.447831 Step: set_fact

2022-05-25 12:26:27.905518 Step: Getting the serviceAccountName

2022-05-25 12:26:28.598581 Step: [Prepare]: Including the litmus LIB for random pod deletion

2022-05-25 12:26:29.438106 Step: [Prepare]: Create helper pod for pod delete chaos
FAILED - RETRYING: [Status]: Checking the running status of the helper pod (90 retries left).
FAILED - RETRYING: [Status]: Checking the running status of the helper pod (89 retries left).
FAILED - RETRYING: [Status]: Checking the running status of the helper pod (88 retries left).

2022-05-25 12:26:37.565679 Step: [Status]: Checking the running status of the helper pod
FAILED - RETRYING: [Status]: Checking whether helper pods is in completed state (25 retries left).
FAILED - RETRYING: [Status]: Checking whether helper pods is in completed state (24 retries left).
FAILED - RETRYING: [Status]: Checking whether helper pods is in completed state (23 retries left).
FAILED - RETRYING: [Status]: Checking whether helper pods is in completed state (22 retries left).
FAILED - RETRYING: [Status]: Checking whether helper pods is in completed state (21 retries left).
FAILED - RETRYING: [Status]: Checking whether helper pods is in completed state (20 retries left).
FAILED - RETRYING: [Status]: Checking whether helper pods is in completed state (19 retries left).
FAILED - RETRYING: [Status]: Checking whether helper pods is in completed state (18 retries left).
FAILED - RETRYING: [Status]: Checking whether helper pods is in completed state (17 retries left).
FAILED - RETRYING: [Status]: Checking whether helper pods is in completed state (16 retries left).
FAILED - RETRYING: [Status]: Checking whether helper pods is in completed state (15 retries left).
FAILED - RETRYING: [Status]: Checking whether helper pods is in completed state (14 retries left).
FAILED - RETRYING: [Status]: Checking whether helper pods is in completed state (13 retries left).
FAILED - RETRYING: [Status]: Checking whether helper pods is in completed state (12 retries left).
FAILED - RETRYING: [Status]: Checking whether helper pods is in completed state (11 retries left).
FAILED - RETRYING: [Status]: Checking whether helper pods is in completed state (10 retries left).
FAILED - RETRYING: [Status]: Checking whether helper pods is in completed state (9 retries left).

2022-05-25 12:27:02.174063 Step: [Status]: Checking whether helper pods is in completed state

2022-05-25 12:27:03.259519 Step: [CleanUP]: Tear down pod delete helper pod

2022-05-25 12:27:03.718349 Step: [Status]: Confirm that the pod delete helper pod is deleted
included: /utils/common/status_app_pod.yml for 127.0.0.1

2022-05-25 12:27:04.381166 Step: [Status]: Checking whether application pods are in running state

2022-05-25 12:27:04.851047 Step: [Status]: Checking whether application containers are in running state
included: /utils/common/status_app_pod.yml for 127.0.0.1

2022-05-25 12:27:05.478304 Step: [Status]: Checking whether application pods are in running state

2022-05-25 12:27:06.030950 Step: [Status]: Checking whether application containers are in running state
included: /utils/common/generate-kubernetes-chaos-events.yml for 127.0.0.1

2022-05-25 12:27:06.477480 Step: [Event]: Obtain the current date in ISO8601 format

2022-05-25 12:27:06.537674 Step: set_fact

2022-05-25 12:27:08.093506 Step: [Event]: Creating a PostChaosCheck event in the chaosengine

2022-05-25 12:27:08.683931 Step: deleting service and pod of nginx

2022-05-25 12:27:09.442472 Step: deleting liveness pod

2022-05-25 12:27:09.495891 Step: set_fact
included: /utils/runtime/getting_failure_step.yml for 127.0.0.1

2022-05-25 12:27:10.065946 Step: [Failure-Detection]: Recording the name of failed step
included: /utils/common/generate-kubernetes-chaos-events.yml for 127.0.0.1

2022-05-25 12:27:10.514844 Step: [Event]: Obtain the current date in ISO8601 format

2022-05-25 12:27:10.587843 Step: set_fact

2022-05-25 12:27:11.982050 Step: [Event]: Creating a Summary event in the chaosengine
included: /utils/runtime/update_chaos_result_resource.yml for 127.0.0.1

2022-05-25 12:27:12.876992 Step: [Result]: Update the chaos result CR to reflect EOT (End of Test)

2022-05-25 12:27:13.658210 Step: [The END]: Apply the chaos result CR for coredns-pod-delete experiment

2022-05-25 12:27:13.694012 ************ RELAX, EXPERIMENT ENDS! ************
127.0.0.1                  : ok=54   changed=33   unreachable=0    failed=0