2023-02-18 03:05:05,166 - INFO - Checking if dcae-datalake-feeder is ready 2023-02-18 03:05:05,263 - ERROR - Exception when calling list_namespaced_pod: (403) Reason: Forbidden HTTP response headers: HTTPHeaderDict({'Audit-Id': 'cadb7091-b05a-4697-bfdc-dc10c652487d', 'Cache-Control': 'no-cache, private', 'Content-Type': 'application/json', 'X-Content-Type-Options': 'nosniff', 'X-Kubernetes-Pf-Flowschema-Uid': 'ecf569da-938b-4d59-a245-d473aba352f9', 'X-Kubernetes-Pf-Prioritylevel-Uid': '68019ac0-ab62-4527-a563-e503c2222181', 'Date': 'Sat, 18 Feb 2023 03:05:06 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-02-18 03:05:11,264 - INFO - Checking if dcae-datalake-feeder is ready 2023-02-18 03:05:11,271 - ERROR - Exception when calling list_namespaced_pod: (403) Reason: Forbidden HTTP response headers: HTTPHeaderDict({'Audit-Id': '0d7499eb-559a-48b6-ae6b-9cdc650d180a', 'Cache-Control': 'no-cache, private', 'Content-Type': 'application/json', 'X-Content-Type-Options': 'nosniff', 'X-Kubernetes-Pf-Flowschema-Uid': 'ecf569da-938b-4d59-a245-d473aba352f9', 'X-Kubernetes-Pf-Prioritylevel-Uid': '68019ac0-ab62-4527-a563-e503c2222181', 'Date': 'Sat, 18 Feb 2023 03:05:12 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-02-18 03:05:19,278 - INFO - Checking if dcae-datalake-feeder is ready 2023-02-18 03:05:19,283 - ERROR - Exception when calling list_namespaced_pod: (403) Reason: Forbidden HTTP response headers: HTTPHeaderDict({'Audit-Id': '1dc54edf-b956-47e4-b280-64614d531dca', 'Cache-Control': 'no-cache, private', 'Content-Type': 'application/json', 'X-Content-Type-Options': 'nosniff', 'X-Kubernetes-Pf-Flowschema-Uid': 'ecf569da-938b-4d59-a245-d473aba352f9', 'X-Kubernetes-Pf-Prioritylevel-Uid': '68019ac0-ab62-4527-a563-e503c2222181', 'Date': 'Sat, 18 Feb 2023 03:05:20 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-02-18 03:05:25,290 - INFO - Checking if dcae-datalake-feeder is ready 2023-02-18 03:05:34,576 - INFO - Deployment onap-dcae-datalake-feeder is NOT ready 2023-02-18 03:05:40,759 - INFO - Checking if dcae-datalake-feeder is ready 2023-02-18 03:05:50,260 - INFO - Deployment onap-dcae-datalake-feeder is NOT ready 2023-02-18 03:05:56,363 - INFO - Checking if dcae-datalake-feeder is ready 2023-02-18 03:06:07,063 - INFO - Deployment onap-dcae-datalake-feeder is NOT ready 2023-02-18 03:06:17,166 - INFO - Checking if dcae-datalake-feeder is ready 2023-02-18 03:06:27,667 - INFO - Deployment onap-dcae-datalake-feeder is NOT ready 2023-02-18 03:06:32,769 - INFO - Checking if dcae-datalake-feeder is ready 2023-02-18 03:06:41,756 - INFO - Deployment onap-dcae-datalake-feeder is NOT ready 2023-02-18 03:06:49,862 - INFO - Checking if dcae-datalake-feeder is ready 2023-02-18 03:06:59,251 - INFO - Deployment onap-dcae-datalake-feeder is NOT ready 2023-02-18 03:07:08,361 - INFO - Checking if dcae-datalake-feeder is ready 2023-02-18 03:07:18,760 - INFO - Deployment onap-dcae-datalake-feeder is NOT ready 2023-02-18 03:07:26,862 - INFO - Checking if dcae-datalake-feeder is ready 2023-02-18 03:07:37,668 - INFO - Deployment onap-dcae-datalake-feeder is NOT ready 2023-02-18 03:07:42,768 - INFO - Checking if dcae-datalake-feeder is ready 2023-02-18 03:07:52,456 - INFO - Deployment onap-dcae-datalake-feeder is NOT ready 2023-02-18 03:07:57,554 - INFO - Checking if dcae-datalake-feeder is ready 2023-02-18 03:08:06,465 - INFO - Deployment onap-dcae-datalake-feeder is NOT ready 2023-02-18 03:08:14,563 - INFO - Checking if dcae-datalake-feeder is ready 2023-02-18 03:08:22,680 - INFO - Deployment onap-dcae-datalake-feeder is NOT ready 2023-02-18 03:08:28,759 - INFO - Checking if dcae-datalake-feeder is ready 2023-02-18 03:08:37,967 - INFO - Deployment onap-dcae-datalake-feeder is NOT ready 2023-02-18 03:08:48,062 - INFO - Checking if dcae-datalake-feeder is ready 2023-02-18 03:08:57,055 - INFO - Deployment onap-dcae-datalake-feeder is NOT ready 2023-02-18 03:09:05,069 - INFO - Checking if dcae-datalake-feeder is ready 2023-02-18 03:09:13,759 - INFO - Deployment onap-dcae-datalake-feeder is ready