By type
2023-02-27 00:21:56,384 - INFO - Checking if dcae-datalake-feeder is ready
2023-02-27 00:21:56,492 - ERROR - Exception when calling list_namespaced_pod: (403)
Reason: Forbidden
HTTP response headers: HTTPHeaderDict({'Audit-Id': 'b69db769-e02a-4045-a755-74637b8185c5', 'Cache-Control': 'no-cache, private', 'Content-Type': 'application/json', 'X-Content-Type-Options': 'nosniff', 'X-Kubernetes-Pf-Flowschema-Uid': 'ace3625b-8a69-4fd4-beae-c955568d9652', 'X-Kubernetes-Pf-Prioritylevel-Uid': '36fcc789-8600-4abc-9b9a-9a7510686076', 'Date': 'Mon, 27 Feb 2023 00:21:57 GMT', 'Content-Length': '358'})
HTTP response body: {"kind":"Status","apiVersion":"v1","metadata":{},"status":"Failure","message":"pods is forbidden: User \"system:serviceaccount:onap:onap-dcae-datalake-des-read\" cannot list resource \"pods\" in API group \"\" in the namespace \"onap\": RBAC: role.rbac.authorization.k8s.io \"onap-read\" not found","reason":"Forbidden","details":{"kind":"pods"},"code":403}
2023-02-27 00:22:04,494 - INFO - Checking if dcae-datalake-feeder is ready
2023-02-27 00:22:04,497 - ERROR - Exception when calling list_namespaced_pod: (403)
Reason: Forbidden
HTTP response headers: HTTPHeaderDict({'Audit-Id': '3e04157b-54f8-4ec5-b6b8-1aa523282c9b', 'Cache-Control': 'no-cache, private', 'Content-Type': 'application/json', 'X-Content-Type-Options': 'nosniff', 'X-Kubernetes-Pf-Flowschema-Uid': 'ace3625b-8a69-4fd4-beae-c955568d9652', 'X-Kubernetes-Pf-Prioritylevel-Uid': '36fcc789-8600-4abc-9b9a-9a7510686076', 'Date': 'Mon, 27 Feb 2023 00:22:05 GMT', 'Content-Length': '358'})
HTTP response body: {"kind":"Status","apiVersion":"v1","metadata":{},"status":"Failure","message":"pods is forbidden: User \"system:serviceaccount:onap:onap-dcae-datalake-des-read\" cannot list resource \"pods\" in API group \"\" in the namespace \"onap\": RBAC: role.rbac.authorization.k8s.io \"onap-read\" not found","reason":"Forbidden","details":{"kind":"pods"},"code":403}
2023-02-27 00:22:14,504 - INFO - Checking if dcae-datalake-feeder is ready
2023-02-27 00:22:14,509 - ERROR - Exception when calling list_namespaced_pod: (403)
Reason: Forbidden
HTTP response headers: HTTPHeaderDict({'Audit-Id': '6815e77f-b903-40ee-a3ba-936169f47d60', 'Cache-Control': 'no-cache, private', 'Content-Type': 'application/json', 'X-Content-Type-Options': 'nosniff', 'X-Kubernetes-Pf-Flowschema-Uid': 'ace3625b-8a69-4fd4-beae-c955568d9652', 'X-Kubernetes-Pf-Prioritylevel-Uid': '36fcc789-8600-4abc-9b9a-9a7510686076', 'Date': 'Mon, 27 Feb 2023 00:22:15 GMT', 'Content-Length': '358'})
HTTP response body: {"kind":"Status","apiVersion":"v1","metadata":{},"status":"Failure","message":"pods is forbidden: User \"system:serviceaccount:onap:onap-dcae-datalake-des-read\" cannot list resource \"pods\" in API group \"\" in the namespace \"onap\": RBAC: role.rbac.authorization.k8s.io \"onap-read\" not found","reason":"Forbidden","details":{"kind":"pods"},"code":403}
2023-02-27 00:22:21,517 - INFO - Checking if dcae-datalake-feeder is ready
2023-02-27 00:22:30,285 - INFO - Deployment onap-dcae-datalake-feeder is NOT ready
2023-02-27 00:22:39,391 - INFO - Checking if dcae-datalake-feeder is ready
2023-02-27 00:22:47,719 - INFO - Deployment onap-dcae-datalake-feeder is NOT ready
2023-02-27 00:22:58,894 - INFO - Checking if dcae-datalake-feeder is ready
2023-02-27 00:23:07,492 - INFO - Deployment onap-dcae-datalake-feeder is NOT ready
2023-02-27 00:23:14,589 - INFO - Checking if dcae-datalake-feeder is ready
2023-02-27 00:23:23,881 - INFO - Deployment onap-dcae-datalake-feeder is NOT ready
2023-02-27 00:23:30,893 - INFO - Checking if dcae-datalake-feeder is ready
2023-02-27 00:23:40,198 - INFO - Deployment onap-dcae-datalake-feeder is NOT ready
2023-02-27 00:23:48,385 - INFO - Checking if dcae-datalake-feeder is ready
2023-02-27 00:23:57,383 - INFO - Deployment onap-dcae-datalake-feeder is NOT ready
2023-02-27 00:24:05,487 - INFO - Checking if dcae-datalake-feeder is ready
2023-02-27 00:24:14,890 - INFO - Deployment onap-dcae-datalake-feeder is NOT ready
2023-02-27 00:24:19,988 - INFO - Checking if dcae-datalake-feeder is ready
2023-02-27 00:24:29,588 - INFO - Deployment onap-dcae-datalake-feeder is NOT ready
2023-02-27 00:24:39,689 - INFO - Checking if dcae-datalake-feeder is ready
2023-02-27 00:24:48,595 - INFO - Deployment onap-dcae-datalake-feeder is NOT ready
2023-02-27 00:24:57,693 - INFO - Checking if dcae-datalake-feeder is ready
2023-02-27 00:25:06,481 - INFO - Deployment onap-dcae-datalake-feeder is NOT ready
2023-02-27 00:25:14,589 - INFO - Checking if dcae-datalake-feeder is ready
2023-02-27 00:25:23,196 - INFO - Deployment onap-dcae-datalake-feeder is NOT ready
2023-02-27 00:25:34,385 - INFO - Checking if dcae-datalake-feeder is ready
2023-02-27 00:25:43,683 - INFO - Deployment onap-dcae-datalake-feeder is NOT ready
2023-02-27 00:25:51,786 - INFO - Checking if dcae-datalake-feeder is ready
2023-02-27 00:26:01,199 - INFO - Deployment onap-dcae-datalake-feeder is NOT ready
2023-02-27 00:26:07,294 - INFO - Checking if dcae-datalake-feeder is ready
2023-02-27 00:26:16,799 - INFO - Deployment onap-dcae-datalake-feeder is NOT ready
2023-02-27 00:26:24,985 - INFO - Checking if dcae-datalake-feeder is ready
2023-02-27 00:26:34,190 - INFO - Deployment onap-dcae-datalake-feeder is NOT ready
2023-02-27 00:26:42,289 - INFO - Checking if dcae-datalake-feeder is ready
2023-02-27 00:26:51,498 - INFO - Deployment onap-dcae-datalake-feeder is NOT ready
2023-02-27 00:27:00,690 - INFO - Checking if dcae-datalake-feeder is ready
2023-02-27 00:27:10,981 - INFO - Deployment onap-dcae-datalake-feeder is NOT ready
2023-02-27 00:27:16,088 - INFO - Checking if dcae-datalake-feeder is ready
2023-02-27 00:27:26,782 - INFO - Deployment onap-dcae-datalake-feeder is NOT ready
2023-02-27 00:27:32,797 - INFO - Checking if dcae-datalake-feeder is ready
2023-02-27 00:27:43,290 - INFO - Deployment onap-dcae-datalake-feeder is NOT ready
2023-02-27 00:27:48,389 - INFO - Checking if dcae-datalake-feeder is ready
2023-02-27 00:27:58,395 - INFO - Deployment onap-dcae-datalake-feeder is ready