2021-08-28 23:01:28,305 - INFO - Checking if aaf-locate is ready
2021-08-28 23:01:28,404 - ERROR - Exception when calling list_namespaced_pod: (403)
Reason: Forbidden
HTTP response headers: HTTPHeaderDict({'Cache-Control': 'no-cache, private', 'Content-Type': 'application/json', 'X-Content-Type-Options': 'nosniff', 'X-Kubernetes-Pf-Flowschema-Uid': '0a9dd822-20ed-4ef8-9614-ea9e7018f5c4', 'X-Kubernetes-Pf-Prioritylevel-Uid': '71b5c281-87b5-4757-8a54-af34757b5836', 'Date': 'Sat, 28 Aug 2021 23:01:28 GMT', 'Content-Length': '358'})
HTTP response body: {"kind":"Status","apiVersion":"v1","metadata":{},"status":"Failure","message":"pods is forbidden: User \"system:serviceaccount:onap:dev-policy-distribution-read\" cannot list resource \"pods\" in API group \"\" in the namespace \"onap\": RBAC: role.rbac.authorization.k8s.io \"dev-read\" not found","reason":"Forbidden","details":{"kind":"pods"},"code":403}



2021-08-28 23:01:37,412 - INFO - Checking if aaf-locate is ready
2021-08-28 23:01:45,902 - INFO - Deployment dev-aaf-locate is ready
2021-08-28 23:01:45,910 - INFO - Checking if aaf-cm is ready
2021-08-28 23:01:52,208 - INFO - Deployment dev-aaf-cm is NOT ready
2021-08-28 23:01:57,216 - INFO - Checking if aaf-cm is ready
2021-08-28 23:02:04,008 - INFO - Deployment dev-aaf-cm is NOT ready
2021-08-28 23:02:14,023 - INFO - Checking if aaf-cm is ready
2021-08-28 23:02:23,012 - INFO - Deployment dev-aaf-cm is NOT ready
2021-08-28 23:02:28,107 - INFO - Checking if aaf-cm is ready
2021-08-28 23:02:36,600 - INFO - Deployment dev-aaf-cm is NOT ready
2021-08-28 23:02:42,611 - INFO - Checking if aaf-cm is ready
2021-08-28 23:02:51,205 - INFO - Deployment dev-aaf-cm is NOT ready
2021-08-28 23:03:00,311 - INFO - Checking if aaf-cm is ready
2021-08-28 23:03:08,810 - INFO - Deployment dev-aaf-cm is NOT ready
2021-08-28 23:03:17,917 - INFO - Checking if aaf-cm is ready
2021-08-28 23:03:27,013 - INFO - Deployment dev-aaf-cm is ready
2021-08-28 23:03:27,104 - INFO - Checking if aaf-service is ready
2021-08-28 23:03:34,507 - INFO - Deployment dev-aaf-service is ready