By type
2023-01-09 03:14:00,923 - INFO - Checking if dcae-datalake-feeder is ready
2023-01-09 03:14:01,030 - ERROR - Exception when calling list_namespaced_pod: (403)
Reason: Forbidden
HTTP response headers: HTTPHeaderDict({'Audit-Id': '5a5c33cd-9977-42b6-9fdf-ec60952cecc1', 'Cache-Control': 'no-cache, private', 'Content-Type': 'application/json', 'X-Content-Type-Options': 'nosniff', 'X-Kubernetes-Pf-Flowschema-Uid': 'd013d211-5b2e-4805-ae9e-77e122ad098c', 'X-Kubernetes-Pf-Prioritylevel-Uid': 'fefdc2cb-0aed-4018-9ff4-0b429ef0e815', 'Date': 'Mon, 09 Jan 2023 03:13:59 GMT', 'Content-Length': '363'})
HTTP response body: {"kind":"Status","apiVersion":"v1","metadata":{},"status":"Failure","message":"pods is forbidden: User \"system:serviceaccount:onap:onap-dcae-datalake-admin-ui-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-01-09 03:14:06,033 - INFO - Checking if dcae-datalake-feeder is ready
2023-01-09 03:14:15,632 - INFO - Deployment onap-dcae-datalake-feeder is NOT ready
2023-01-09 03:14:23,729 - INFO - Checking if dcae-datalake-feeder is ready
2023-01-09 03:14:32,628 - INFO - Deployment onap-dcae-datalake-feeder is NOT ready
2023-01-09 03:14:42,733 - INFO - Checking if dcae-datalake-feeder is ready
2023-01-09 03:14:52,031 - INFO - Deployment onap-dcae-datalake-feeder is NOT ready
2023-01-09 03:15:00,133 - INFO - Checking if dcae-datalake-feeder is ready
2023-01-09 03:15:09,339 - INFO - Deployment onap-dcae-datalake-feeder is NOT ready
2023-01-09 03:15:16,438 - INFO - Checking if dcae-datalake-feeder is ready
2023-01-09 03:15:26,532 - INFO - Deployment onap-dcae-datalake-feeder is NOT ready
2023-01-09 03:15:36,637 - INFO - Checking if dcae-datalake-feeder is ready
2023-01-09 03:15:46,322 - INFO - Deployment onap-dcae-datalake-feeder is NOT ready
2023-01-09 03:15:51,425 - INFO - Checking if dcae-datalake-feeder is ready
2023-01-09 03:16:00,732 - INFO - Deployment onap-dcae-datalake-feeder is NOT ready
2023-01-09 03:16:05,829 - INFO - Checking if dcae-datalake-feeder is ready
2023-01-09 03:16:15,221 - INFO - Deployment onap-dcae-datalake-feeder is NOT ready
2023-01-09 03:16:22,324 - INFO - Checking if dcae-datalake-feeder is ready
2023-01-09 03:16:31,524 - INFO - Deployment onap-dcae-datalake-feeder is NOT ready
2023-01-09 03:16:36,621 - INFO - Checking if dcae-datalake-feeder is ready
2023-01-09 03:16:45,926 - INFO - Deployment onap-dcae-datalake-feeder is NOT ready
2023-01-09 03:16:55,027 - INFO - Checking if dcae-datalake-feeder is ready
2023-01-09 03:17:05,739 - INFO - Deployment onap-dcae-datalake-feeder is NOT ready
2023-01-09 03:17:13,833 - INFO - Checking if dcae-datalake-feeder is ready
2023-01-09 03:17:23,621 - INFO - Deployment onap-dcae-datalake-feeder is NOT ready
2023-01-09 03:17:34,729 - INFO - Checking if dcae-datalake-feeder is ready
2023-01-09 03:17:44,430 - INFO - Deployment onap-dcae-datalake-feeder is NOT ready
2023-01-09 03:17:49,525 - INFO - Checking if dcae-datalake-feeder is ready
2023-01-09 03:17:59,223 - INFO - Deployment onap-dcae-datalake-feeder is NOT ready
2023-01-09 03:18:05,233 - INFO - Checking if dcae-datalake-feeder is ready
2023-01-09 03:18:16,159 - INFO - Deployment onap-dcae-datalake-feeder is NOT ready
2023-01-09 03:18:21,325 - INFO - Checking if dcae-datalake-feeder is ready
2023-01-09 03:18:31,637 - INFO - Deployment onap-dcae-datalake-feeder is ready