Kraken pod kill scenario - attempted execution on one node, hits another instead

[Noreen21]

2023-04-30 20:37:05,480 [INFO] Starting kraken 2023-04-30 20:37:05,487 [INFO] Initializing client to talk to the Kubernetes cluster 2023-04-30 20:37:06,769 [INFO] Publishing kraken status at http://0.0.0.0:8086 2023-04-30 20:37:06,769 [INFO] Publishing kraken status at http://0.0.0.0:8086 2023-04-30 20:37:06,770 [INFO] Starting http server at http://0.0.0.0:8086

2023-04-30 20:37:06,770 [INFO] Fetching cluster info 2023-04-30 20:37:06,792 [INFO] Cluster version is 4.12.14 2023-04-30 20:37:06,792 [INFO] Server URL: https://api.e28-h31-r750.example.com:6443 2023-04-30 20:37:06,793 [INFO] Generated a uuid for the run: 03dc38c9-3757-442b-8b01-ad6060a2c03b 2023-04-30 20:37:06,793 [INFO] Daemon mode not enabled, will run through 1 iterations

2023-04-30 20:37:06,793 [INFO] Executing scenarios for iteration 0 2023-04-30 20:37:06,793 [INFO] connection set up 2023-04-30 20:37:06,793 [INFO] response RUN 2023-04-30 20:37:06,793 [INFO] scenario scenarios/openshift/01_etcd.yml 2023-04-30 20:37:07,904 [INFO] { "output_id": "success", "output_data": { "pods": { "1682887026899055361": { "namespace": "openshift-etcd", "name": "etcd-e28-h35-r750" } } } }

Contents of 01_etcd.yaml:

# yaml-language-server: $schema=../plugin.schema.json
- id: kill-pods
  config:
    namespace_pattern: ^openshift-etcd$
    label_selector: k8s-app=etcd
- id: wait-for-pods
  config:
    namespace_pattern: ^openshift-etcd$
    label_selector: k8s-app=etcd
    count: 1

config file:

kraken:
    distribution: openshift                                # Distribution can be kubernetes or openshift
    kubeconfig_path: /root/sno/e28-h31-r750/kubeconfig                        # Path to kubeconfig
    exit_on_failure: False                                 # Exit when a post action scenario fails
    publish_kraken_status: True                            # Can be accessed at http://0.0.0.0:8081
    signal_state: RUN                                      # Will wait for the RUN signal when set to PAUSE before running the scenarios, refer docs/signal.md for more details
    signal_address: 0.0.0.0                                # Signal listening address
    port: 8086                                             # Signal port
    litmus_install: True                                   # Installs specified version, set to False if it's already setup
    litmus_version: v1.13.6                                # Litmus version to install
    litmus_uninstall: False                                # If you want to uninstall litmus if failure
    litmus_uninstall_before_run: True                      # If you want to uninstall litmus before a new run starts
    chaos_scenarios:                                       # List of policies/chaos scenarios to load
            -   plugin_scenarios:
                - scenarios/openshift/01_etcd.yml