2022-06-18 05:03:25,459 - INFO - Checking if aaf-locate is ready
2022-06-18 05:03:25,566 - ERROR - Exception when calling list_namespaced_pod: (403)
Reason: Forbidden
HTTP response headers: HTTPHeaderDict({'Audit-Id': '3e18a170-cddd-4051-ac1c-d06dd325d20f', 'Cache-Control': 'no-cache, private', 'Content-Type': 'application/json', 'X-Content-Type-Options': 'nosniff', 'X-Kubernetes-Pf-Flowschema-Uid': '57afd881-962d-440b-987e-4a3698c8fe26', 'X-Kubernetes-Pf-Prioritylevel-Uid': '06b18b75-e393-44d5-9ff2-5e02e115390c', 'Date': 'Sat, 18 Jun 2022 05:03:25 GMT', 'Content-Length': '355'})
HTTP response body: {"kind":"Status","apiVersion":"v1","metadata":{},"status":"Failure","message":"pods is forbidden: User \"system:serviceaccount:onap:onap-message-router-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-06-18 05:03:35,576 - INFO - Checking if aaf-locate is ready
2022-06-18 05:03:35,581 - ERROR - Exception when calling list_namespaced_pod: (403)
Reason: Forbidden
HTTP response headers: HTTPHeaderDict({'Audit-Id': '403650dd-459d-4f25-b6b8-34a14a5d1f12', 'Cache-Control': 'no-cache, private', 'Content-Type': 'application/json', 'X-Content-Type-Options': 'nosniff', 'X-Kubernetes-Pf-Flowschema-Uid': '57afd881-962d-440b-987e-4a3698c8fe26', 'X-Kubernetes-Pf-Prioritylevel-Uid': '06b18b75-e393-44d5-9ff2-5e02e115390c', 'Date': 'Sat, 18 Jun 2022 05:03:35 GMT', 'Content-Length': '355'})
HTTP response body: {"kind":"Status","apiVersion":"v1","metadata":{},"status":"Failure","message":"pods is forbidden: User \"system:serviceaccount:onap:onap-message-router-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-06-18 05:03:41,587 - INFO - Checking if aaf-locate is ready
2022-06-18 05:03:41,591 - ERROR - Exception when calling list_namespaced_pod: (403)
Reason: Forbidden
HTTP response headers: HTTPHeaderDict({'Audit-Id': 'c3265572-5caf-4a84-91f3-57bda9fd8907', 'Cache-Control': 'no-cache, private', 'Content-Type': 'application/json', 'X-Content-Type-Options': 'nosniff', 'X-Kubernetes-Pf-Flowschema-Uid': '57afd881-962d-440b-987e-4a3698c8fe26', 'X-Kubernetes-Pf-Prioritylevel-Uid': '06b18b75-e393-44d5-9ff2-5e02e115390c', 'Date': 'Sat, 18 Jun 2022 05:03:41 GMT', 'Content-Length': '355'})
HTTP response body: {"kind":"Status","apiVersion":"v1","metadata":{},"status":"Failure","message":"pods is forbidden: User \"system:serviceaccount:onap:onap-message-router-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-06-18 05:03:46,596 - INFO - Checking if aaf-locate is ready
2022-06-18 05:03:46,599 - ERROR - Exception when calling list_namespaced_pod: (403)
Reason: Forbidden
HTTP response headers: HTTPHeaderDict({'Audit-Id': '3aee3d5e-5702-4347-99c4-2e07a8b8e3e8', 'Cache-Control': 'no-cache, private', 'Content-Type': 'application/json', 'X-Content-Type-Options': 'nosniff', 'X-Kubernetes-Pf-Flowschema-Uid': '57afd881-962d-440b-987e-4a3698c8fe26', 'X-Kubernetes-Pf-Prioritylevel-Uid': '06b18b75-e393-44d5-9ff2-5e02e115390c', 'Date': 'Sat, 18 Jun 2022 05:03:46 GMT', 'Content-Length': '355'})
HTTP response body: {"kind":"Status","apiVersion":"v1","metadata":{},"status":"Failure","message":"pods is forbidden: User \"system:serviceaccount:onap:onap-message-router-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-06-18 05:03:51,605 - INFO - Checking if aaf-locate is ready
2022-06-18 05:03:57,675 - INFO - Deployment onap-aaf-locate is ready
2022-06-18 05:03:57,756 - INFO - Checking if aaf-cm is ready
2022-06-18 05:04:03,671 - INFO - Deployment onap-aaf-cm is ready
2022-06-18 05:04:03,755 - INFO - Checking if aaf-service is ready
2022-06-18 05:04:10,055 - INFO - Deployment onap-aaf-service is ready