2023-01-05 23:02:11,999 - INFO - Checking if cds-blueprints-processor is ready 2023-01-05 23:02:12,013 - ERROR - Exception when calling list_namespaced_pod: (403) Reason: Forbidden HTTP response headers: HTTPHeaderDict({'Audit-Id': 'defc0096-1557-4b82-90bf-d5094bcb90e9', 'Cache-Control': 'no-cache, private', 'Content-Type': 'application/json', 'X-Content-Type-Options': 'nosniff', 'X-Kubernetes-Pf-Flowschema-Uid': 'c5c09948-24ba-4422-ba4a-ae09b5f93f95', 'X-Kubernetes-Pf-Prioritylevel-Uid': '64d68a83-3b8e-4703-89b1-02e525506ba3', 'Date': 'Thu, 05 Jan 2023 23:02:11 GMT', 'Content-Length': '361'}) HTTP response body: {"kind":"Status","apiVersion":"v1","metadata":{},"status":"Failure","message":"pods is forbidden: User \"system:serviceaccount:onap:onap-cds-command-executor-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-05 23:02:21,020 - INFO - Checking if cds-blueprints-processor is ready 2023-01-05 23:02:21,024 - ERROR - Exception when calling list_namespaced_pod: (403) Reason: Forbidden HTTP response headers: HTTPHeaderDict({'Audit-Id': '5f2e4523-8bd3-43c1-a3dc-0e5121204e95', 'Cache-Control': 'no-cache, private', 'Content-Type': 'application/json', 'X-Content-Type-Options': 'nosniff', 'X-Kubernetes-Pf-Flowschema-Uid': 'c5c09948-24ba-4422-ba4a-ae09b5f93f95', 'X-Kubernetes-Pf-Prioritylevel-Uid': '64d68a83-3b8e-4703-89b1-02e525506ba3', 'Date': 'Thu, 05 Jan 2023 23:02:21 GMT', 'Content-Length': '361'}) HTTP response body: {"kind":"Status","apiVersion":"v1","metadata":{},"status":"Failure","message":"pods is forbidden: User \"system:serviceaccount:onap:onap-cds-command-executor-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-05 23:02:29,029 - INFO - Checking if cds-blueprints-processor is ready 2023-01-05 23:02:29,033 - ERROR - Exception when calling list_namespaced_pod: (403) Reason: Forbidden HTTP response headers: HTTPHeaderDict({'Audit-Id': '2cb30eee-74ed-4b29-b376-e29959293c19', 'Cache-Control': 'no-cache, private', 'Content-Type': 'application/json', 'X-Content-Type-Options': 'nosniff', 'X-Kubernetes-Pf-Flowschema-Uid': 'c5c09948-24ba-4422-ba4a-ae09b5f93f95', 'X-Kubernetes-Pf-Prioritylevel-Uid': '64d68a83-3b8e-4703-89b1-02e525506ba3', 'Date': 'Thu, 05 Jan 2023 23:02:29 GMT', 'Content-Length': '361'}) HTTP response body: {"kind":"Status","apiVersion":"v1","metadata":{},"status":"Failure","message":"pods is forbidden: User \"system:serviceaccount:onap:onap-cds-command-executor-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-05 23:02:34,039 - INFO - Checking if cds-blueprints-processor is ready 2023-01-05 23:02:34,936 - INFO - Deployment onap-cds-blueprints-processor is NOT ready 2023-01-05 23:02:40,948 - INFO - Checking if cds-blueprints-processor is ready 2023-01-05 23:02:41,787 - INFO - Deployment onap-cds-blueprints-processor is NOT ready 2023-01-05 23:02:47,797 - INFO - Checking if cds-blueprints-processor is ready 2023-01-05 23:02:48,637 - INFO - Deployment onap-cds-blueprints-processor is NOT ready 2023-01-05 23:02:57,655 - INFO - Checking if cds-blueprints-processor is ready 2023-01-05 23:02:58,599 - INFO - Deployment onap-cds-blueprints-processor is NOT ready 2023-01-05 23:03:09,617 - INFO - Checking if cds-blueprints-processor is ready 2023-01-05 23:03:10,470 - INFO - Deployment onap-cds-blueprints-processor is NOT ready 2023-01-05 23:03:16,482 - INFO - Checking if cds-blueprints-processor is ready 2023-01-05 23:03:17,433 - INFO - Deployment onap-cds-blueprints-processor is NOT ready 2023-01-05 23:03:27,449 - INFO - Checking if cds-blueprints-processor is ready 2023-01-05 23:03:28,652 - INFO - Deployment onap-cds-blueprints-processor is NOT ready 2023-01-05 23:03:35,667 - INFO - Checking if cds-blueprints-processor is ready 2023-01-05 23:03:36,554 - INFO - Deployment onap-cds-blueprints-processor is NOT ready 2023-01-05 23:03:41,564 - INFO - Checking if cds-blueprints-processor is ready 2023-01-05 23:03:42,439 - INFO - Deployment onap-cds-blueprints-processor is NOT ready 2023-01-05 23:03:47,449 - INFO - Checking if cds-blueprints-processor is ready 2023-01-05 23:03:48,359 - INFO - Deployment onap-cds-blueprints-processor is NOT ready 2023-01-05 23:03:57,377 - INFO - Checking if cds-blueprints-processor is ready 2023-01-05 23:03:58,308 - INFO - Deployment onap-cds-blueprints-processor is NOT ready 2023-01-05 23:04:03,323 - INFO - Checking if cds-blueprints-processor is ready 2023-01-05 23:04:04,238 - INFO - Deployment onap-cds-blueprints-processor is NOT ready 2023-01-05 23:04:13,253 - INFO - Checking if cds-blueprints-processor is ready 2023-01-05 23:04:14,149 - INFO - Deployment onap-cds-blueprints-processor is NOT ready 2023-01-05 23:04:19,161 - INFO - Checking if cds-blueprints-processor is ready 2023-01-05 23:04:20,058 - INFO - Deployment onap-cds-blueprints-processor is NOT ready 2023-01-05 23:04:30,077 - INFO - Checking if cds-blueprints-processor is ready 2023-01-05 23:04:31,134 - INFO - Deployment onap-cds-blueprints-processor is NOT ready 2023-01-05 23:04:40,151 - INFO - Checking if cds-blueprints-processor is ready 2023-01-05 23:04:41,126 - INFO - Deployment onap-cds-blueprints-processor is NOT ready 2023-01-05 23:04:49,141 - INFO - Checking if cds-blueprints-processor is ready 2023-01-05 23:04:50,103 - INFO - Deployment onap-cds-blueprints-processor is NOT ready 2023-01-05 23:04:58,117 - INFO - Checking if cds-blueprints-processor is ready 2023-01-05 23:04:59,040 - INFO - Deployment onap-cds-blueprints-processor is NOT ready 2023-01-05 23:05:04,055 - INFO - Checking if cds-blueprints-processor is ready 2023-01-05 23:05:05,003 - INFO - Deployment onap-cds-blueprints-processor is NOT ready 2023-01-05 23:05:13,020 - INFO - Checking if cds-blueprints-processor is ready 2023-01-05 23:05:13,942 - INFO - Deployment onap-cds-blueprints-processor is NOT ready 2023-01-05 23:05:18,954 - INFO - Checking if cds-blueprints-processor is ready 2023-01-05 23:05:19,921 - INFO - Deployment onap-cds-blueprints-processor is ready