Results

          2022-05-28 05:00:26,441 - INFO - Checking if aaf-locate is ready
2022-05-28 05:00:26,554 - ERROR - Exception when calling list_namespaced_pod: (403)
Reason: Forbidden
HTTP response headers: HTTPHeaderDict({'Audit-Id': '3fa2f24f-6c1b-4c13-96ce-7682f0121224', 'Cache-Control': 'no-cache, private', 'Content-Type': 'application/json', 'X-Content-Type-Options': 'nosniff', 'X-Kubernetes-Pf-Flowschema-Uid': '788cbc0d-5dd4-4c7f-9758-a8ec917eef3f', 'X-Kubernetes-Pf-Prioritylevel-Uid': '7b0511bb-c7f1-4f36-ad1f-e49ca5907478', 'Date': 'Sat, 28 May 2022 05:00:27 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-05-28 05:00:31,559 - INFO - Checking if aaf-locate is ready
2022-05-28 05:00:40,643 - INFO - Deployment onap-aaf-locate is ready
2022-05-28 05:00:40,740 - INFO - Checking if aaf-cm is ready
2022-05-28 05:00:49,044 - INFO - Deployment onap-aaf-cm is ready
2022-05-28 05:00:49,139 - INFO - Checking if aaf-service is ready
2022-05-28 05:00:58,446 - INFO - Deployment onap-aaf-service is ready