2023-02-03 03:14:03,884 - INFO - Checking if message-router is ready
2023-02-03 03:14:03,989 - ERROR - Exception when calling list_namespaced_pod: (403)
Reason: Forbidden
HTTP response headers: HTTPHeaderDict({'Audit-Id': 'ba85d817-ddbb-45dc-866c-77910d726c63', 'Cache-Control': 'no-cache, private', 'Content-Type': 'application/json', 'X-Content-Type-Options': 'nosniff', 'X-Kubernetes-Pf-Flowschema-Uid': '213dabd5-3456-4e14-b1dc-c789eba0bc4f', 'X-Kubernetes-Pf-Prioritylevel-Uid': 'c651490f-76e9-4158-8557-1dc146681211', 'Date': 'Fri, 03 Feb 2023 03:14:04 GMT', 'Content-Length': '365'})
HTTP response body: {"kind":"Status","apiVersion":"v1","metadata":{},"status":"Failure","message":"pods is forbidden: User \"system:serviceaccount:onap:onap-dcae-ves-openapi-manager-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-03 03:14:08,995 - INFO - Checking if message-router is ready
2023-02-03 03:14:08,999 - ERROR - Exception when calling list_namespaced_pod: (403)
Reason: Forbidden
HTTP response headers: HTTPHeaderDict({'Audit-Id': '7156255c-dc8d-4c09-9c44-65a308239bf8', 'Cache-Control': 'no-cache, private', 'Content-Type': 'application/json', 'X-Content-Type-Options': 'nosniff', 'X-Kubernetes-Pf-Flowschema-Uid': '213dabd5-3456-4e14-b1dc-c789eba0bc4f', 'X-Kubernetes-Pf-Prioritylevel-Uid': 'c651490f-76e9-4158-8557-1dc146681211', 'Date': 'Fri, 03 Feb 2023 03:14:09 GMT', 'Content-Length': '365'})
HTTP response body: {"kind":"Status","apiVersion":"v1","metadata":{},"status":"Failure","message":"pods is forbidden: User \"system:serviceaccount:onap:onap-dcae-ves-openapi-manager-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-03 03:14:14,004 - INFO - Checking if message-router is ready
2023-02-03 03:14:14,008 - ERROR - Exception when calling list_namespaced_pod: (403)
Reason: Forbidden
HTTP response headers: HTTPHeaderDict({'Audit-Id': 'b66b6065-759d-4d6f-a2e1-2982e94c7963', 'Cache-Control': 'no-cache, private', 'Content-Type': 'application/json', 'X-Content-Type-Options': 'nosniff', 'X-Kubernetes-Pf-Flowschema-Uid': '213dabd5-3456-4e14-b1dc-c789eba0bc4f', 'X-Kubernetes-Pf-Prioritylevel-Uid': 'c651490f-76e9-4158-8557-1dc146681211', 'Date': 'Fri, 03 Feb 2023 03:14:14 GMT', 'Content-Length': '365'})
HTTP response body: {"kind":"Status","apiVersion":"v1","metadata":{},"status":"Failure","message":"pods is forbidden: User \"system:serviceaccount:onap:onap-dcae-ves-openapi-manager-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-03 03:14:19,012 - INFO - Checking if message-router is ready
2023-02-03 03:14:19,016 - ERROR - Exception when calling list_namespaced_pod: (403)
Reason: Forbidden
HTTP response headers: HTTPHeaderDict({'Audit-Id': 'b2d3aa60-2588-46fb-b788-242c678cb2ab', 'Cache-Control': 'no-cache, private', 'Content-Type': 'application/json', 'X-Content-Type-Options': 'nosniff', 'X-Kubernetes-Pf-Flowschema-Uid': '213dabd5-3456-4e14-b1dc-c789eba0bc4f', 'X-Kubernetes-Pf-Prioritylevel-Uid': 'c651490f-76e9-4158-8557-1dc146681211', 'Date': 'Fri, 03 Feb 2023 03:14:19 GMT', 'Content-Length': '365'})
HTTP response body: {"kind":"Status","apiVersion":"v1","metadata":{},"status":"Failure","message":"pods is forbidden: User \"system:serviceaccount:onap:onap-dcae-ves-openapi-manager-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-03 03:14:25,022 - INFO - Checking if message-router is ready
2023-02-03 03:14:25,026 - ERROR - Exception when calling list_namespaced_pod: (403)
Reason: Forbidden
HTTP response headers: HTTPHeaderDict({'Audit-Id': '4b2d6ddf-046c-4a16-a937-383598017ca7', 'Cache-Control': 'no-cache, private', 'Content-Type': 'application/json', 'X-Content-Type-Options': 'nosniff', 'X-Kubernetes-Pf-Flowschema-Uid': '213dabd5-3456-4e14-b1dc-c789eba0bc4f', 'X-Kubernetes-Pf-Prioritylevel-Uid': 'c651490f-76e9-4158-8557-1dc146681211', 'Date': 'Fri, 03 Feb 2023 03:14:25 GMT', 'Content-Length': '365'})
HTTP response body: {"kind":"Status","apiVersion":"v1","metadata":{},"status":"Failure","message":"pods is forbidden: User \"system:serviceaccount:onap:onap-dcae-ves-openapi-manager-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-03 03:14:31,034 - INFO - Checking if message-router is ready
2023-02-03 03:14:40,988 - INFO - Statefulset onap-message-router is NOT ready
2023-02-03 03:14:50,090 - INFO - Checking if message-router is ready
2023-02-03 03:14:59,385 - INFO - Statefulset onap-message-router is NOT ready
2023-02-03 03:15:05,490 - INFO - Checking if message-router is ready
2023-02-03 03:15:14,879 - INFO - Statefulset onap-message-router is NOT ready
2023-02-03 03:15:25,996 - INFO - Checking if message-router is ready
2023-02-03 03:15:36,589 - INFO - Statefulset onap-message-router is NOT ready
2023-02-03 03:15:46,691 - INFO - Checking if message-router is ready
2023-02-03 03:15:56,789 - INFO - Statefulset onap-message-router is NOT ready
2023-02-03 03:16:04,982 - INFO - Checking if message-router is ready
2023-02-03 03:16:15,880 - INFO - Statefulset onap-message-router is NOT ready
2023-02-03 03:16:26,990 - INFO - Checking if message-router is ready
2023-02-03 03:16:36,792 - INFO - Statefulset onap-message-router is NOT ready
2023-02-03 03:16:44,886 - INFO - Checking if message-router is ready
2023-02-03 03:16:55,077 - INFO - Statefulset onap-message-router is NOT ready
2023-02-03 03:17:00,185 - INFO - Checking if message-router is ready
2023-02-03 03:17:10,188 - INFO - Statefulset onap-message-router is NOT ready
2023-02-03 03:17:16,282 - INFO - Checking if message-router is ready
2023-02-03 03:17:25,490 - INFO - Statefulset onap-message-router is NOT ready
2023-02-03 03:17:35,591 - INFO - Checking if message-router is ready
2023-02-03 03:17:45,085 - INFO - Statefulset onap-message-router is NOT ready
2023-02-03 03:17:56,190 - INFO - Checking if message-router is ready
2023-02-03 03:18:07,283 - INFO - Statefulset onap-message-router is NOT ready
2023-02-03 03:18:13,482 - INFO - Checking if message-router is ready
2023-02-03 03:18:24,779 - INFO - Statefulset onap-message-router is NOT ready
2023-02-03 03:18:33,886 - INFO - Checking if message-router is ready
2023-02-03 03:18:45,980 - INFO - Statefulset onap-message-router is NOT ready
2023-02-03 03:18:54,084 - INFO - Checking if message-router is ready
2023-02-03 03:19:05,081 - INFO - Statefulset onap-message-router is ready
2023-02-03 03:19:05,177 - INFO - Checking if sdc-be is ready
2023-02-03 03:19:18,480 - INFO - Deployment onap-sdc-be is NOT ready
2023-02-03 03:19:24,586 - INFO - Checking if sdc-be is ready
2023-02-03 03:19:37,178 - INFO - Deployment onap-sdc-be is NOT ready
2023-02-03 03:19:45,290 - INFO - Checking if sdc-be is ready
2023-02-03 03:19:58,084 - INFO - Deployment onap-sdc-be is NOT ready
2023-02-03 03:20:06,195 - INFO - Checking if sdc-be is ready
2023-02-03 03:20:18,595 - INFO - Deployment onap-sdc-be is NOT ready
2023-02-03 03:20:24,687 - INFO - Checking if sdc-be is ready
2023-02-03 03:20:37,480 - INFO - Deployment onap-sdc-be is NOT ready
2023-02-03 03:20:42,590 - INFO - Checking if sdc-be is ready
2023-02-03 03:20:55,286 - INFO - Deployment onap-sdc-be is NOT ready
2023-02-03 03:21:06,390 - INFO - Checking if sdc-be is ready
2023-02-03 03:21:18,490 - INFO - Deployment onap-sdc-be is NOT ready
2023-02-03 03:21:23,586 - INFO - Checking if sdc-be is ready
2023-02-03 03:21:36,482 - INFO - Deployment onap-sdc-be is NOT ready
2023-02-03 03:21:45,592 - INFO - Checking if sdc-be is ready
2023-02-03 03:21:58,385 - INFO - Deployment onap-sdc-be is NOT ready
2023-02-03 03:22:08,590 - INFO - Checking if sdc-be is ready
2023-02-03 03:22:21,393 - INFO - Deployment onap-sdc-be is NOT ready
2023-02-03 03:22:32,494 - INFO - Checking if sdc-be is ready
2023-02-03 03:22:45,992 - INFO - Deployment onap-sdc-be is NOT ready
2023-02-03 03:22:55,090 - INFO - Checking if sdc-be is ready
2023-02-03 03:23:07,682 - INFO - Deployment onap-sdc-be is NOT ready
2023-02-03 03:23:12,787 - INFO - Checking if sdc-be is ready
2023-02-03 03:23:24,879 - INFO - Deployment onap-sdc-be is NOT ready
2023-02-03 03:23:29,986 - INFO - Checking if sdc-be is ready
2023-02-03 03:23:42,392 - INFO - Deployment onap-sdc-be is NOT ready
2023-02-03 03:23:51,492 - INFO - Checking if sdc-be is ready
2023-02-03 03:24:03,497 - INFO - Deployment onap-sdc-be is NOT ready
2023-02-03 03:24:13,594 - INFO - Checking if sdc-be is ready
2023-02-03 03:24:25,391 - INFO - Deployment onap-sdc-be is NOT ready
2023-02-03 03:24:33,490 - INFO - Checking if sdc-be is ready
2023-02-03 03:24:45,196 - INFO - Deployment onap-sdc-be is NOT ready
2023-02-03 03:24:56,289 - INFO - Checking if sdc-be is ready
2023-02-03 03:25:08,678 - INFO - Deployment onap-sdc-be is NOT ready
2023-02-03 03:25:14,784 - INFO - Checking if sdc-be is ready
2023-02-03 03:25:26,982 - INFO - Deployment onap-sdc-be is NOT ready
2023-02-03 03:25:33,088 - INFO - Checking if sdc-be is ready
2023-02-03 03:25:44,181 - INFO - Deployment onap-sdc-be is NOT ready
2023-02-03 03:25:50,286 - INFO - Checking if sdc-be is ready
2023-02-03 03:26:02,083 - INFO - Deployment onap-sdc-be is NOT ready
2023-02-03 03:26:13,191 - INFO - Checking if sdc-be is ready
2023-02-03 03:26:24,881 - INFO - Deployment onap-sdc-be is NOT ready
2023-02-03 03:26:34,990 - INFO - Checking if sdc-be is ready
2023-02-03 03:26:45,986 - INFO - Deployment onap-sdc-be is ready