2022-04-26 05:04:11,930 - INFO - Checking if aaf-locate is ready 2022-04-26 05:04:12,031 - ERROR - Exception when calling list_namespaced_pod: (403) Reason: Forbidden HTTP response headers: HTTPHeaderDict({'Audit-Id': 'eb5781cf-1357-4963-8fba-155d5ae651ee', 'Cache-Control': 'no-cache, private', 'Content-Type': 'application/json', 'X-Content-Type-Options': 'nosniff', 'X-Kubernetes-Pf-Flowschema-Uid': '717e4ea2-7436-413c-96c3-79b1c2c37278', 'X-Kubernetes-Pf-Prioritylevel-Uid': 'f87da6b0-c438-4093-a6f0-987ee1af4bf8', 'Date': 'Tue, 26 Apr 2022 05:04:11 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-26 05:04:23,042 - INFO - Checking if aaf-locate is ready 2022-04-26 05:04:23,046 - ERROR - Exception when calling list_namespaced_pod: (403) Reason: Forbidden HTTP response headers: HTTPHeaderDict({'Audit-Id': '03a05d5f-1ff1-4d52-8f9a-0020a5ff9a9b', 'Cache-Control': 'no-cache, private', 'Content-Type': 'application/json', 'X-Content-Type-Options': 'nosniff', 'X-Kubernetes-Pf-Flowschema-Uid': '717e4ea2-7436-413c-96c3-79b1c2c37278', 'X-Kubernetes-Pf-Prioritylevel-Uid': 'f87da6b0-c438-4093-a6f0-987ee1af4bf8', 'Date': 'Tue, 26 Apr 2022 05:04:22 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-26 05:04:34,054 - INFO - Checking if aaf-locate is ready 2022-04-26 05:04:34,057 - ERROR - Exception when calling list_namespaced_pod: (403) Reason: Forbidden HTTP response headers: HTTPHeaderDict({'Audit-Id': 'ceb34d38-4e2b-4e1a-80de-8d49af6bb9f5', 'Cache-Control': 'no-cache, private', 'Content-Type': 'application/json', 'X-Content-Type-Options': 'nosniff', 'X-Kubernetes-Pf-Flowschema-Uid': '717e4ea2-7436-413c-96c3-79b1c2c37278', 'X-Kubernetes-Pf-Prioritylevel-Uid': 'f87da6b0-c438-4093-a6f0-987ee1af4bf8', 'Date': 'Tue, 26 Apr 2022 05:04:33 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-26 05:04:39,063 - INFO - Checking if aaf-locate is ready 2022-04-26 05:04:45,360 - INFO - Deployment onap-aaf-locate is ready 2022-04-26 05:04:45,431 - INFO - Checking if aaf-cm is ready 2022-04-26 05:04:52,139 - INFO - Deployment onap-aaf-cm is ready 2022-04-26 05:04:52,230 - INFO - Checking if aaf-service is ready 2022-04-26 05:04:59,828 - INFO - Deployment onap-aaf-service is ready