2023-02-27 11:22:16,069 - INFO - Checking if dmaap-bc is ready
2023-02-27 11:22:16,377 - ERROR - Exception when calling list_namespaced_pod: (403)
Reason: Forbidden
HTTP response headers: HTTPHeaderDict({'Audit-Id': 'cb713a5f-7949-49ce-9355-035164fab350', '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 11:22:17 GMT', 'Content-Length': '364'})
HTTP response body: {"kind":"Status","apiVersion":"v1","metadata":{},"status":"Failure","message":"pods is forbidden: User \"system:serviceaccount:onap:onap-dcae-datafile-collector-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 11:22:22,382 - INFO - Checking if dmaap-bc is ready
2023-02-27 11:22:38,262 - INFO - Deployment onap-dmaap-bc is NOT ready
2023-02-27 11:22:46,370 - INFO - Checking if dmaap-bc is ready
2023-02-27 11:23:02,268 - INFO - Deployment onap-dmaap-bc is NOT ready
2023-02-27 11:23:08,390 - INFO - Checking if dmaap-bc is ready
2023-02-27 11:23:23,664 - INFO - Deployment onap-dmaap-bc is NOT ready
2023-02-27 11:23:33,876 - INFO - Checking if dmaap-bc is ready
2023-02-27 11:23:49,465 - INFO - Deployment onap-dmaap-bc is NOT ready
2023-02-27 11:23:55,773 - INFO - Checking if dmaap-bc is ready
2023-02-27 11:24:11,469 - INFO - Deployment onap-dmaap-bc is NOT ready
2023-02-27 11:24:22,666 - INFO - Checking if dmaap-bc is ready
2023-02-27 11:24:36,257 - INFO - Deployment onap-dmaap-bc is NOT ready
2023-02-27 11:24:43,364 - INFO - Checking if dmaap-bc is ready
2023-02-27 11:24:58,266 - INFO - Deployment onap-dmaap-bc is NOT ready
2023-02-27 11:25:08,566 - INFO - Checking if dmaap-bc is ready
2023-02-27 11:25:24,959 - INFO - Deployment onap-dmaap-bc is NOT ready
2023-02-27 11:25:31,162 - INFO - Checking if dmaap-bc is ready
2023-02-27 11:25:47,858 - INFO - Deployment onap-dmaap-bc is NOT ready
2023-02-27 11:25:55,968 - INFO - Checking if dmaap-bc is ready
2023-02-27 11:26:13,657 - INFO - Deployment onap-dmaap-bc is NOT ready
2023-02-27 11:26:22,775 - INFO - Checking if dmaap-bc is ready
2023-02-27 11:26:36,173 - INFO - Deployment onap-dmaap-bc is NOT ready
2023-02-27 11:26:44,376 - INFO - Checking if dmaap-bc is ready
2023-02-27 11:27:01,870 - INFO - Deployment onap-dmaap-bc is NOT ready
2023-02-27 11:27:11,066 - INFO - Checking if dmaap-bc is ready
2023-02-27 11:27:30,667 - INFO - Deployment onap-dmaap-bc is NOT ready
2023-02-27 11:27:41,868 - INFO - Checking if dmaap-bc is ready
2023-02-27 11:28:04,364 - INFO - Deployment onap-dmaap-bc is NOT ready
2023-02-27 11:28:09,564 - INFO - Checking if dmaap-bc is ready
2023-02-27 11:28:32,758 - INFO - Deployment onap-dmaap-bc is NOT ready
2023-02-27 11:28:40,965 - INFO - Checking if dmaap-bc is ready
2023-02-27 11:29:03,069 - INFO - Deployment onap-dmaap-bc is ready
2023-02-27 11:29:03,259 - INFO - Checking if dmaap-provisioning-job is ready
2023-02-27 11:29:25,562 - INFO - Checking if onap-dmaap-bc-dmaap-provisioning is complete
2023-02-27 11:29:25,759 - INFO - onap-dmaap-bc-dmaap-provisioning is complete
2023-02-27 11:29:25,962 - INFO - Checking if message-router is ready
2023-02-27 11:29:48,356 - INFO - Statefulset onap-message-router is ready