Results

          2022-05-01 05:01:48,604 - INFO - Checking if aaf-locate is ready
2022-05-01 05:01:48,717 - ERROR - Exception when calling list_namespaced_pod: (403)
Reason: Forbidden
HTTP response headers: HTTPHeaderDict({'Audit-Id': '4bcd21ea-3fb8-4450-b6ac-2844da9132d7', 'Cache-Control': 'no-cache, private', 'Content-Type': 'application/json', 'X-Content-Type-Options': 'nosniff', 'X-Kubernetes-Pf-Flowschema-Uid': 'e11b5320-5fd9-4fd3-884c-36a6fc13eeda', 'X-Kubernetes-Pf-Prioritylevel-Uid': 'f6ee06c3-9ca2-4e17-aea2-eebd0ed32c4b', 'Date': 'Sun, 01 May 2022 05:01:48 GMT', 'Content-Length': '349'})
HTTP response body: {"kind":"Status","apiVersion":"v1","metadata":{},"status":"Failure","message":"pods is forbidden: User \"system:serviceaccount:onap:onap-dmaap-bc-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-05-01 05:01:56,725 - INFO - Checking if aaf-locate is ready
2022-05-01 05:01:56,731 - ERROR - Exception when calling list_namespaced_pod: (403)
Reason: Forbidden
HTTP response headers: HTTPHeaderDict({'Audit-Id': '270ef032-2699-4509-a265-22f5b35abc11', 'Cache-Control': 'no-cache, private', 'Content-Type': 'application/json', 'X-Content-Type-Options': 'nosniff', 'X-Kubernetes-Pf-Flowschema-Uid': 'e11b5320-5fd9-4fd3-884c-36a6fc13eeda', 'X-Kubernetes-Pf-Prioritylevel-Uid': 'f6ee06c3-9ca2-4e17-aea2-eebd0ed32c4b', 'Date': 'Sun, 01 May 2022 05:01:56 GMT', 'Content-Length': '349'})
HTTP response body: {"kind":"Status","apiVersion":"v1","metadata":{},"status":"Failure","message":"pods is forbidden: User \"system:serviceaccount:onap:onap-dmaap-bc-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-05-01 05:02:01,736 - INFO - Checking if aaf-locate is ready
2022-05-01 05:02:01,740 - ERROR - Exception when calling list_namespaced_pod: (403)
Reason: Forbidden
HTTP response headers: HTTPHeaderDict({'Audit-Id': 'eb9c5c39-f781-4b4a-901c-e2b71d19d383', 'Cache-Control': 'no-cache, private', 'Content-Type': 'application/json', 'X-Content-Type-Options': 'nosniff', 'X-Kubernetes-Pf-Flowschema-Uid': 'e11b5320-5fd9-4fd3-884c-36a6fc13eeda', 'X-Kubernetes-Pf-Prioritylevel-Uid': 'f6ee06c3-9ca2-4e17-aea2-eebd0ed32c4b', 'Date': 'Sun, 01 May 2022 05:02:01 GMT', 'Content-Length': '349'})
HTTP response body: {"kind":"Status","apiVersion":"v1","metadata":{},"status":"Failure","message":"pods is forbidden: User \"system:serviceaccount:onap:onap-dmaap-bc-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-05-01 05:02:09,749 - INFO - Checking if aaf-locate is ready
2022-05-01 05:02:09,754 - ERROR - Exception when calling list_namespaced_pod: (403)
Reason: Forbidden
HTTP response headers: HTTPHeaderDict({'Audit-Id': '8acfc290-bce8-4ced-8984-589cf73681db', 'Cache-Control': 'no-cache, private', 'Content-Type': 'application/json', 'X-Content-Type-Options': 'nosniff', 'X-Kubernetes-Pf-Flowschema-Uid': 'e11b5320-5fd9-4fd3-884c-36a6fc13eeda', 'X-Kubernetes-Pf-Prioritylevel-Uid': 'f6ee06c3-9ca2-4e17-aea2-eebd0ed32c4b', 'Date': 'Sun, 01 May 2022 05:02:09 GMT', 'Content-Length': '349'})
HTTP response body: {"kind":"Status","apiVersion":"v1","metadata":{},"status":"Failure","message":"pods is forbidden: User \"system:serviceaccount:onap:onap-dmaap-bc-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-05-01 05:02:19,761 - INFO - Checking if aaf-locate is ready
2022-05-01 05:02:27,219 - INFO - Deployment onap-aaf-locate is ready
2022-05-01 05:02:27,304 - INFO - Checking if aaf-cm is ready
2022-05-01 05:02:34,407 - INFO - Deployment onap-aaf-cm is ready
2022-05-01 05:02:34,501 - INFO - Checking if aaf-service is ready
2022-05-01 05:02:41,902 - INFO - Deployment onap-aaf-service is ready