Results

          2023-01-13 11:39:02,326 - INFO - Checking if aaf-locate is ready
2023-01-13 11:39:02,439 - ERROR - Exception when calling list_namespaced_pod: (403)
Reason: Forbidden
HTTP response headers: HTTPHeaderDict({'Audit-Id': '6661816e-9503-4b50-bca0-e0750a9d3b1a', 'Cache-Control': 'no-cache, private', 'Content-Type': 'application/json', 'X-Content-Type-Options': 'nosniff', 'X-Kubernetes-Pf-Flowschema-Uid': 'f156bb81-958c-4502-8ef1-9a48a75ef0f0', 'X-Kubernetes-Pf-Prioritylevel-Uid': '802270f3-a0b1-449d-8dc5-0c79605ad96b', 'Date': 'Fri, 13 Jan 2023 11:39:02 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}



2023-01-13 11:39:11,444 - INFO - Checking if aaf-locate is ready
2023-01-13 11:39:11,451 - ERROR - Exception when calling list_namespaced_pod: (403)
Reason: Forbidden
HTTP response headers: HTTPHeaderDict({'Audit-Id': 'b44e6005-2385-4f1c-bde4-059e28526ced', 'Cache-Control': 'no-cache, private', 'Content-Type': 'application/json', 'X-Content-Type-Options': 'nosniff', 'X-Kubernetes-Pf-Flowschema-Uid': 'f156bb81-958c-4502-8ef1-9a48a75ef0f0', 'X-Kubernetes-Pf-Prioritylevel-Uid': '802270f3-a0b1-449d-8dc5-0c79605ad96b', 'Date': 'Fri, 13 Jan 2023 11:39:11 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}



2023-01-13 11:39:20,461 - INFO - Checking if aaf-locate is ready
2023-01-13 11:39:20,525 - ERROR - Exception when calling list_namespaced_pod: (403)
Reason: Forbidden
HTTP response headers: HTTPHeaderDict({'Audit-Id': 'c18a8e46-72f0-4c98-9b51-8663da059384', 'Cache-Control': 'no-cache, private', 'Content-Type': 'application/json', 'X-Content-Type-Options': 'nosniff', 'X-Kubernetes-Pf-Flowschema-Uid': 'f156bb81-958c-4502-8ef1-9a48a75ef0f0', 'X-Kubernetes-Pf-Prioritylevel-Uid': '802270f3-a0b1-449d-8dc5-0c79605ad96b', 'Date': 'Fri, 13 Jan 2023 11:39:20 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}



2023-01-13 11:39:30,532 - INFO - Checking if aaf-locate is ready
2023-01-13 11:39:30,539 - ERROR - Exception when calling list_namespaced_pod: (403)
Reason: Forbidden
HTTP response headers: HTTPHeaderDict({'Audit-Id': 'fd5bd70f-32ab-4f3a-9dcf-254863fc4919', 'Cache-Control': 'no-cache, private', 'Content-Type': 'application/json', 'X-Content-Type-Options': 'nosniff', 'X-Kubernetes-Pf-Flowschema-Uid': 'f156bb81-958c-4502-8ef1-9a48a75ef0f0', 'X-Kubernetes-Pf-Prioritylevel-Uid': '802270f3-a0b1-449d-8dc5-0c79605ad96b', 'Date': 'Fri, 13 Jan 2023 11:39:30 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}



2023-01-13 11:39:35,544 - INFO - Checking if aaf-locate is ready
2023-01-13 11:39:54,836 - INFO - Deployment onap-aaf-locate is ready
2023-01-13 11:39:54,943 - INFO - Checking if aaf-cm is ready
2023-01-13 11:40:12,141 - INFO - Deployment onap-aaf-cm is ready
2023-01-13 11:40:12,238 - INFO - Checking if aaf-service is ready
2023-01-13 11:40:35,036 - INFO - Deployment onap-aaf-service is ready