pod scenario fails because it "cannot list resource "pods""
lugi0 opened this issue · comments
Luca Giorgi commented
When running a pod scenario, I get the following error:
2023-04-13 11:55:14,011 [INFO] {
"output_id": "error",
"output_data": {
"error": "Traceback (most recent call last):\n File \"/home/lgiorgi/Work/krkn/krkn_venv/lib64/python3.11/site-packages/arcaflow_plugin_kill_pod.py\", line 169, in kill_pods\n pods = _find_pods(\n ^^^^^^^^^^^\n File \"/home/lgiorgi/Work/krkn/krkn_venv/lib64/python3.11/site-packages/arcaflow_plugin_kill_pod.py\", line 39, in _find_pods\n pod_response: V1PodList = core_v1.list_pod_for_all_namespaces(\n ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^\n File \"/home/lgiorgi/Work/krkn/krkn_venv/lib64/python3.11/site-packages/kubernetes/client/api/core_v1_api.py\", line 17309, in list_pod_for_all_namespaces\n return self.list_pod_for_all_namespaces_with_http_info(**kwargs) # noqa: E501\n ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^\n File \"/home/lgiorgi/Work/krkn/krkn_venv/lib64/python3.11/site-packages/kubernetes/client/api/core_v1_api.py\", line 17416, in list_pod_for_all_namespaces_with_http_info\n return self.api_client.call_api(\n ^^^^^^^^^^^^^^^^^^^^^^^^^\n File \"/home/lgiorgi/Work/krkn/krkn_venv/lib64/python3.11/site-packages/kubernetes/client/api_client.py\", line 348, in call_api\n return self.__call_api(resource_path, method,\n ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^\n File \"/home/lgiorgi/Work/krkn/krkn_venv/lib64/python3.11/site-packages/kubernetes/client/api_client.py\", line 180, in __call_api\n response_data = self.request(\n ^^^^^^^^^^^^^\n File \"/home/lgiorgi/Work/krkn/krkn_venv/lib64/python3.11/site-packages/kubernetes/client/api_client.py\", line 373, in request\n return self.rest_client.GET(url,\n ^^^^^^^^^^^^^^^^^^^^^^^^^\n File \"/home/lgiorgi/Work/krkn/krkn_venv/lib64/python3.11/site-packages/kubernetes/client/rest.py\", line 241, in GET\n return self.request(\"GET\", url,\n ^^^^^^^^^^^^^^^^^^^^^^^^\n File \"/home/lgiorgi/Work/krkn/krkn_venv/lib64/python3.11/site-packages/kubernetes/client/rest.py\", line 235, in request\n raise ApiException(http_resp=r)\nkubernetes.client.exceptions.ApiException: (403)\nReason: Forbidden\nHTTP response headers: HTTPHeaderDict({'Audit-Id': 'fa6da46b-8ef5-4316-ad26-effa07bf34e4', 'Cache-Control': 'no-cache, private', 'Content-Type': 'application/json', 'Strict-Transport-Security': 'max-age=31536000; includeSubDomains; preload', 'X-Content-Type-Options': 'nosniff', 'X-Kubernetes-Pf-Flowschema-Uid': 'b24ba835-ed79-4350-aeda-c4faedceb68e', 'X-Kubernetes-Pf-Prioritylevel-Uid': 'd6a3592b-909d-4e85-80e7-81a507c64494', 'Date': 'Thu, 13 Apr 2023 09:55:13 GMT', 'Content-Length': '253'})\nHTTP response body: {\"kind\":\"Status\",\"apiVersion\":\"v1\",\"metadata\":{},\"status\":\"Failure\",\"message\":\"pods is forbidden: User \\\"system:anonymous\\\" cannot list resource \\\"pods\\\" in API group \\\"\\\" at the cluster scope\",\"reason\":\"Forbidden\",\"details\":{\"kind\":\"pods\"},\"code\":403}\n\n\n"
}
}
The issues appears to be that this arcaflow plugin does not use the correct kube config when compared to krkn, which is able to communicate with the cluster.
Naga Ravi Chaitanya Elluri commented
cc: @tsebastiani