2022-04-17 01:34:03,604 - INFO - Checking if aaf-locate is ready
2022-04-17 01:34:03,712 - ERROR - Exception when calling list_namespaced_pod: (403)
Reason: Forbidden
HTTP response headers: HTTPHeaderDict({'Audit-Id': '72a1641e-8232-4fac-8b7e-50e1bd9a5fff', 'Cache-Control': 'no-cache, private', 'Content-Type': 'application/json', 'X-Content-Type-Options': 'nosniff', 'X-Kubernetes-Pf-Flowschema-Uid': '68d6f1ec-e1d9-4841-9bf7-138e5695d9b5', 'X-Kubernetes-Pf-Prioritylevel-Uid': 'c99a0ff6-6745-4888-8222-f8058dcaf966', 'Date': 'Sun, 17 Apr 2022 01:34:03 GMT', 'Content-Length': '344'})
HTTP response body: {"kind":"Status","apiVersion":"v1","metadata":{},"status":"Failure","message":"pods is forbidden: User \"system:serviceaccount:onap:onap-nbi-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-04-17 01:34:09,719 - INFO - Checking if aaf-locate is ready
2022-04-17 01:34:09,724 - ERROR - Exception when calling list_namespaced_pod: (403)
Reason: Forbidden
HTTP response headers: HTTPHeaderDict({'Audit-Id': '1fc776be-5046-48dd-bcde-104e9c147c0c', 'Cache-Control': 'no-cache, private', 'Content-Type': 'application/json', 'X-Content-Type-Options': 'nosniff', 'X-Kubernetes-Pf-Flowschema-Uid': '68d6f1ec-e1d9-4841-9bf7-138e5695d9b5', 'X-Kubernetes-Pf-Prioritylevel-Uid': 'c99a0ff6-6745-4888-8222-f8058dcaf966', 'Date': 'Sun, 17 Apr 2022 01:34:09 GMT', 'Content-Length': '344'})
HTTP response body: {"kind":"Status","apiVersion":"v1","metadata":{},"status":"Failure","message":"pods is forbidden: User \"system:serviceaccount:onap:onap-nbi-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-04-17 01:34:15,730 - INFO - Checking if aaf-locate is ready
2022-04-17 01:34:15,736 - ERROR - Exception when calling list_namespaced_pod: (403)
Reason: Forbidden
HTTP response headers: HTTPHeaderDict({'Audit-Id': '282659da-ad44-4e94-8363-71b69c891ff9', 'Cache-Control': 'no-cache, private', 'Content-Type': 'application/json', 'X-Content-Type-Options': 'nosniff', 'X-Kubernetes-Pf-Flowschema-Uid': '68d6f1ec-e1d9-4841-9bf7-138e5695d9b5', 'X-Kubernetes-Pf-Prioritylevel-Uid': 'c99a0ff6-6745-4888-8222-f8058dcaf966', 'Date': 'Sun, 17 Apr 2022 01:34:15 GMT', 'Content-Length': '344'})
HTTP response body: {"kind":"Status","apiVersion":"v1","metadata":{},"status":"Failure","message":"pods is forbidden: User \"system:serviceaccount:onap:onap-nbi-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-04-17 01:34:23,744 - INFO - Checking if aaf-locate is ready
2022-04-17 01:34:23,749 - ERROR - Exception when calling list_namespaced_pod: (403)
Reason: Forbidden
HTTP response headers: HTTPHeaderDict({'Audit-Id': '051fdf4f-ede9-443c-9f85-69f49cb8a231', 'Cache-Control': 'no-cache, private', 'Content-Type': 'application/json', 'X-Content-Type-Options': 'nosniff', 'X-Kubernetes-Pf-Flowschema-Uid': '68d6f1ec-e1d9-4841-9bf7-138e5695d9b5', 'X-Kubernetes-Pf-Prioritylevel-Uid': 'c99a0ff6-6745-4888-8222-f8058dcaf966', 'Date': 'Sun, 17 Apr 2022 01:34:23 GMT', 'Content-Length': '344'})
HTTP response body: {"kind":"Status","apiVersion":"v1","metadata":{},"status":"Failure","message":"pods is forbidden: User \"system:serviceaccount:onap:onap-nbi-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-04-17 01:34:33,759 - INFO - Checking if aaf-locate is ready
2022-04-17 01:34:40,503 - INFO - Deployment onap-aaf-locate is ready
2022-04-17 01:34:40,599 - INFO - Checking if aaf-cm is ready
2022-04-17 01:34:47,506 - INFO - Deployment onap-aaf-cm is ready
2022-04-17 01:34:47,597 - INFO - Checking if aaf-service is ready
2022-04-17 01:34:54,017 - INFO - Deployment onap-aaf-service is ready