Results

          2023-01-03 05:03:36,593 - INFO - Checking if aaf-locate is ready
2023-01-03 05:03:36,694 - ERROR - Exception when calling list_namespaced_pod: (403)
Reason: Forbidden
HTTP response headers: HTTPHeaderDict({'Audit-Id': 'ab99baa9-4a45-4505-9f96-0f4efc2059fa', 'Cache-Control': 'no-cache, private', 'Content-Type': 'application/json', 'X-Content-Type-Options': 'nosniff', 'X-Kubernetes-Pf-Flowschema-Uid': '494b7bb2-cd78-43fe-ac9a-9641b6481183', 'X-Kubernetes-Pf-Prioritylevel-Uid': '8333fa00-2506-40a3-affb-9487d1bf1649', 'Date': 'Tue, 03 Jan 2023 05:03:37 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-03 05:03:45,701 - INFO - Checking if aaf-locate is ready
2023-01-03 05:03:45,705 - ERROR - Exception when calling list_namespaced_pod: (403)
Reason: Forbidden
HTTP response headers: HTTPHeaderDict({'Audit-Id': '8946008a-3d02-48d2-927a-156be1f1ca58', 'Cache-Control': 'no-cache, private', 'Content-Type': 'application/json', 'X-Content-Type-Options': 'nosniff', 'X-Kubernetes-Pf-Flowschema-Uid': '494b7bb2-cd78-43fe-ac9a-9641b6481183', 'X-Kubernetes-Pf-Prioritylevel-Uid': '8333fa00-2506-40a3-affb-9487d1bf1649', 'Date': 'Tue, 03 Jan 2023 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}



2023-01-03 05:03:51,712 - INFO - Checking if aaf-locate is ready
2023-01-03 05:04:02,496 - INFO - Deployment onap-aaf-locate is ready
2023-01-03 05:04:02,597 - INFO - Checking if aaf-cm is ready
2023-01-03 05:04:13,790 - INFO - Deployment onap-aaf-cm is ready
2023-01-03 05:04:13,799 - INFO - Checking if aaf-service is ready
2023-01-03 05:04:25,696 - INFO - Deployment onap-aaf-service is ready