By type
2023-03-01 01:22:19,206 - INFO - Checking if dcae-datalake-feeder is ready
2023-03-01 01:22:19,406 - ERROR - Exception when calling list_namespaced_pod: (403)
Reason: Forbidden
HTTP response headers: HTTPHeaderDict({'Audit-Id': 'f8204187-5fff-4d77-afdb-4f6ead1257a0', 'Cache-Control': 'no-cache, private', 'Content-Type': 'application/json', 'X-Content-Type-Options': 'nosniff', 'X-Kubernetes-Pf-Flowschema-Uid': 'aae1324d-246f-4ddc-83f8-b04b194765ae', 'X-Kubernetes-Pf-Prioritylevel-Uid': 'f6649a6c-488b-464f-83c7-48c92270351f', 'Date': 'Wed, 01 Mar 2023 01:22:19 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-03-01 01:22:25,412 - INFO - Checking if dcae-datalake-feeder is ready
2023-03-01 01:22:35,406 - INFO - Deployment onap-dcae-datalake-feeder is NOT ready
2023-03-01 01:22:40,506 - INFO - Checking if dcae-datalake-feeder is ready
2023-03-01 01:22:51,498 - INFO - Deployment onap-dcae-datalake-feeder is NOT ready
2023-03-01 01:23:01,606 - INFO - Checking if dcae-datalake-feeder is ready
2023-03-01 01:23:12,408 - INFO - Deployment onap-dcae-datalake-feeder is NOT ready
2023-03-01 01:23:18,599 - INFO - Checking if dcae-datalake-feeder is ready
2023-03-01 01:23:29,803 - INFO - Deployment onap-dcae-datalake-feeder is NOT ready
2023-03-01 01:23:37,910 - INFO - Checking if dcae-datalake-feeder is ready
2023-03-01 01:23:48,712 - INFO - Deployment onap-dcae-datalake-feeder is NOT ready
2023-03-01 01:23:54,902 - INFO - Checking if dcae-datalake-feeder is ready
2023-03-01 01:24:06,214 - INFO - Deployment onap-dcae-datalake-feeder is NOT ready
2023-03-01 01:24:16,406 - INFO - Checking if dcae-datalake-feeder is ready
2023-03-01 01:24:27,209 - INFO - Deployment onap-dcae-datalake-feeder is NOT ready
2023-03-01 01:24:35,310 - INFO - Checking if dcae-datalake-feeder is ready
2023-03-01 01:24:46,506 - INFO - Deployment onap-dcae-datalake-feeder is NOT ready
2023-03-01 01:24:55,610 - INFO - Checking if dcae-datalake-feeder is ready
2023-03-01 01:25:06,118 - INFO - Deployment onap-dcae-datalake-feeder is NOT ready
2023-03-01 01:25:11,209 - INFO - Checking if dcae-datalake-feeder is ready
2023-03-01 01:25:22,499 - INFO - Deployment onap-dcae-datalake-feeder is NOT ready
2023-03-01 01:25:28,609 - INFO - Checking if dcae-datalake-feeder is ready
2023-03-01 01:25:39,912 - INFO - Deployment onap-dcae-datalake-feeder is NOT ready
2023-03-01 01:25:50,118 - INFO - Checking if dcae-datalake-feeder is ready
2023-03-01 01:26:01,105 - INFO - Deployment onap-dcae-datalake-feeder is NOT ready
2023-03-01 01:26:06,310 - INFO - Checking if dcae-datalake-feeder is ready
2023-03-01 01:26:17,406 - INFO - Deployment onap-dcae-datalake-feeder is NOT ready
2023-03-01 01:26:24,510 - INFO - Checking if dcae-datalake-feeder is ready
2023-03-01 01:26:35,199 - INFO - Deployment onap-dcae-datalake-feeder is ready