Results

By type

          2022-02-02 00:26:04,301 - INFO - Checking if aaf-locate is ready
2022-02-02 00:26:04,504 - ERROR - Exception when calling list_namespaced_pod: (403)
Reason: Forbidden
HTTP response headers: HTTPHeaderDict({'Audit-Id': '2fd89ab3-b006-403c-9006-cad6ebeb0ff0', 'Cache-Control': 'no-cache, private', 'Content-Type': 'application/json', 'X-Content-Type-Options': 'nosniff', 'X-Kubernetes-Pf-Flowschema-Uid': '802e8931-f384-482d-afac-0ec7e74fdd0a', 'X-Kubernetes-Pf-Prioritylevel-Uid': 'b11ec917-85fd-40c8-be91-3d7ee3b8e931', 'Date': 'Wed, 02 Feb 2022 00:26:04 GMT', 'Content-Length': '354'})
HTTP response body: {"kind":"Status","apiVersion":"v1","metadata":{},"status":"Failure","message":"pods is forbidden: User \"system:serviceaccount:onap:onap-aai-traversal-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}



2022-02-02 00:26:10,510 - INFO - Checking if aaf-locate is ready
2022-02-02 00:26:10,516 - ERROR - Exception when calling list_namespaced_pod: (403)
Reason: Forbidden
HTTP response headers: HTTPHeaderDict({'Audit-Id': 'be04b305-587c-4346-a250-e68c0fe95085', 'Cache-Control': 'no-cache, private', 'Content-Type': 'application/json', 'X-Content-Type-Options': 'nosniff', 'X-Kubernetes-Pf-Flowschema-Uid': '802e8931-f384-482d-afac-0ec7e74fdd0a', 'X-Kubernetes-Pf-Prioritylevel-Uid': 'b11ec917-85fd-40c8-be91-3d7ee3b8e931', 'Date': 'Wed, 02 Feb 2022 00:26:10 GMT', 'Content-Length': '354'})
HTTP response body: {"kind":"Status","apiVersion":"v1","metadata":{},"status":"Failure","message":"pods is forbidden: User \"system:serviceaccount:onap:onap-aai-traversal-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}



2022-02-02 00:26:17,523 - INFO - Checking if aaf-locate is ready
2022-02-02 00:26:17,528 - ERROR - Exception when calling list_namespaced_pod: (403)
Reason: Forbidden
HTTP response headers: HTTPHeaderDict({'Audit-Id': '6fa0d972-d525-4d85-8710-5ddc0197609a', 'Cache-Control': 'no-cache, private', 'Content-Type': 'application/json', 'X-Content-Type-Options': 'nosniff', 'X-Kubernetes-Pf-Flowschema-Uid': '802e8931-f384-482d-afac-0ec7e74fdd0a', 'X-Kubernetes-Pf-Prioritylevel-Uid': 'b11ec917-85fd-40c8-be91-3d7ee3b8e931', 'Date': 'Wed, 02 Feb 2022 00:26:17 GMT', 'Content-Length': '354'})
HTTP response body: {"kind":"Status","apiVersion":"v1","metadata":{},"status":"Failure","message":"pods is forbidden: User \"system:serviceaccount:onap:onap-aai-traversal-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}



2022-02-02 00:26:25,534 - INFO - Checking if aaf-locate is ready
2022-02-02 00:26:28,492 - INFO - Deployment onap-aaf-locate is NOT ready
2022-02-02 00:26:39,502 - INFO - Checking if aaf-locate is ready
2022-02-02 00:26:42,203 - INFO - Deployment onap-aaf-locate is NOT ready
2022-02-02 00:26:50,206 - INFO - Checking if aaf-locate is ready
2022-02-02 00:26:53,290 - INFO - Deployment onap-aaf-locate is NOT ready
2022-02-02 00:27:03,303 - INFO - Checking if aaf-locate is ready
2022-02-02 00:27:06,296 - INFO - Deployment onap-aaf-locate is NOT ready
2022-02-02 00:27:14,307 - INFO - Checking if aaf-locate is ready
2022-02-02 00:27:17,193 - INFO - Deployment onap-aaf-locate is NOT ready
2022-02-02 00:27:23,195 - INFO - Checking if aaf-locate is ready
2022-02-02 00:27:26,413 - INFO - Deployment onap-aaf-locate is NOT ready
2022-02-02 00:27:36,502 - INFO - Checking if aaf-locate is ready
2022-02-02 00:27:39,898 - INFO - Deployment onap-aaf-locate is NOT ready
2022-02-02 00:27:47,999 - INFO - Checking if aaf-locate is ready
2022-02-02 00:27:51,195 - INFO - Deployment onap-aaf-locate is NOT ready
2022-02-02 00:27:56,205 - INFO - Checking if aaf-locate is ready
2022-02-02 00:27:59,694 - INFO - Deployment onap-aaf-locate is NOT ready
2022-02-02 00:28:10,708 - INFO - Checking if aaf-locate is ready
2022-02-02 00:28:13,905 - INFO - Deployment onap-aaf-locate is NOT ready
2022-02-02 00:28:21,992 - INFO - Checking if aaf-locate is ready
2022-02-02 00:28:25,496 - INFO - Deployment onap-aaf-locate is NOT ready
2022-02-02 00:28:33,506 - INFO - Checking if aaf-locate is ready
2022-02-02 00:28:36,597 - INFO - Deployment onap-aaf-locate is NOT ready
2022-02-02 00:28:47,611 - INFO - Checking if aaf-locate is ready
2022-02-02 00:28:50,890 - INFO - Deployment onap-aaf-locate is NOT ready
2022-02-02 00:28:59,902 - INFO - Checking if aaf-locate is ready
2022-02-02 00:29:03,107 - INFO - Deployment onap-aaf-locate is NOT ready
2022-02-02 00:29:14,120 - INFO - Checking if aaf-locate is ready
2022-02-02 00:29:18,207 - INFO - Deployment onap-aaf-locate is NOT ready
2022-02-02 00:29:26,299 - INFO - Checking if aaf-locate is ready
2022-02-02 00:29:30,505 - INFO - Deployment onap-aaf-locate is NOT ready
2022-02-02 00:29:38,602 - INFO - Checking if aaf-locate is ready
2022-02-02 00:29:42,896 - INFO - Deployment onap-aaf-locate is NOT ready
2022-02-02 00:29:47,996 - INFO - Checking if aaf-locate is ready
2022-02-02 00:29:52,796 - INFO - Deployment onap-aaf-locate is NOT ready
2022-02-02 00:30:02,810 - INFO - Checking if aaf-locate is ready
2022-02-02 00:30:07,297 - INFO - Deployment onap-aaf-locate is NOT ready
2022-02-02 00:30:17,306 - INFO - Checking if aaf-locate is ready
2022-02-02 00:30:22,402 - INFO - Deployment onap-aaf-locate is NOT ready
2022-02-02 00:30:31,405 - INFO - Checking if aaf-locate is ready
2022-02-02 00:30:36,393 - INFO - Deployment onap-aaf-locate is NOT ready
2022-02-02 00:30:42,402 - INFO - Checking if aaf-locate is ready
2022-02-02 00:30:47,094 - INFO - Deployment onap-aaf-locate is NOT ready
2022-02-02 00:30:54,105 - INFO - Checking if aaf-locate is ready
2022-02-02 00:30:59,604 - INFO - Deployment onap-aaf-locate is NOT ready
2022-02-02 00:31:04,613 - INFO - Checking if aaf-locate is ready
2022-02-02 00:31:09,604 - INFO - Deployment onap-aaf-locate is NOT ready
2022-02-02 00:31:18,702 - INFO - Checking if aaf-locate is ready
2022-02-02 00:31:24,013 - INFO - Deployment onap-aaf-locate is NOT ready
2022-02-02 00:31:34,102 - INFO - Checking if aaf-locate is ready
2022-02-02 00:31:39,713 - INFO - Deployment onap-aaf-locate is NOT ready
2022-02-02 00:31:47,804 - INFO - Checking if aaf-locate is ready
2022-02-02 00:31:53,297 - INFO - Deployment onap-aaf-locate is NOT ready
2022-02-02 00:32:03,312 - INFO - Checking if aaf-locate is ready
2022-02-02 00:32:08,994 - INFO - Deployment onap-aaf-locate is NOT ready
2022-02-02 00:32:15,004 - INFO - Checking if aaf-locate is ready
2022-02-02 00:32:20,907 - INFO - Deployment onap-aaf-locate is NOT ready
2022-02-02 00:32:29,998 - INFO - Checking if aaf-locate is ready
2022-02-02 00:32:35,814 - INFO - Deployment onap-aaf-locate is ready
2022-02-02 00:32:35,895 - INFO - Checking if aaf-cm is ready
2022-02-02 00:32:41,796 - INFO - Deployment onap-aaf-cm is NOT ready
2022-02-02 00:32:47,897 - INFO - Checking if aaf-cm is ready
2022-02-02 00:32:53,895 - INFO - Deployment onap-aaf-cm is NOT ready
2022-02-02 00:33:03,908 - INFO - Checking if aaf-cm is ready
2022-02-02 00:33:09,697 - INFO - Deployment onap-aaf-cm is NOT ready
2022-02-02 00:33:16,708 - INFO - Checking if aaf-cm is ready
2022-02-02 00:33:22,795 - INFO - Deployment onap-aaf-cm is NOT ready
2022-02-02 00:33:33,810 - INFO - Checking if aaf-cm is ready
2022-02-02 00:33:39,704 - INFO - Deployment onap-aaf-cm is NOT ready
2022-02-02 00:33:45,714 - INFO - Checking if aaf-cm is ready
2022-02-02 00:33:51,492 - INFO - Deployment onap-aaf-cm is NOT ready
2022-02-02 00:33:59,504 - INFO - Checking if aaf-cm is ready
2022-02-02 00:34:05,816 - INFO - Deployment onap-aaf-cm is NOT ready
2022-02-02 00:34:14,902 - INFO - Checking if aaf-cm is ready
2022-02-02 00:34:21,092 - INFO - Deployment onap-aaf-cm is ready
2022-02-02 00:34:21,096 - INFO - Checking if aaf-service is ready
2022-02-02 00:34:26,796 - INFO - Deployment onap-aaf-service is ready