Results

          2023-02-01 04:00:24,335 - INFO - Checking if aaf-locate is ready
2023-02-01 04:00:24,441 - ERROR - Exception when calling list_namespaced_pod: (403)
Reason: Forbidden
HTTP response headers: HTTPHeaderDict({'Audit-Id': '9d1a2faf-f7f9-4c7f-b815-a1123d13a875', 'Cache-Control': 'no-cache, private', 'Content-Type': 'application/json', 'X-Content-Type-Options': 'nosniff', 'X-Kubernetes-Pf-Flowschema-Uid': '02014025-87fd-497e-a034-dd195c0023e1', 'X-Kubernetes-Pf-Prioritylevel-Uid': '1671854d-8a72-4dbd-929e-95e3cfe87548', 'Date': 'Wed, 01 Feb 2023 04:00:23 GMT', 'Content-Length': '344'})
HTTP response body: {"kind":"Status","apiVersion":"v1","metadata":{},"status":"Failure","message":"pods is forbidden: User \"system:serviceaccount:onap:onap-cli-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-02-01 04:00:35,453 - INFO - Checking if aaf-locate is ready
2023-02-01 04:00:42,831 - INFO - Deployment onap-aaf-locate is ready
2023-02-01 04:00:42,837 - INFO - Checking if aaf-cm is ready
2023-02-01 04:00:50,331 - INFO - Deployment onap-aaf-cm is ready
2023-02-01 04:00:50,428 - INFO - Checking if aaf-service is ready
2023-02-01 04:00:57,732 - INFO - Deployment onap-aaf-service is ready