Results

By type
Logs
raw version
          2023-01-12 05:05:44,111 - INFO - Checking if dcae-datalake-feeder is ready
2023-01-12 05:05:44,217 - ERROR - Exception when calling list_namespaced_pod: (403)
Reason: Forbidden
HTTP response headers: HTTPHeaderDict({'Audit-Id': '3f7b0e3d-0b0d-49c0-8b0f-e6b6f7499985', 'Cache-Control': 'no-cache, private', 'Content-Type': 'application/json', 'X-Content-Type-Options': 'nosniff', 'X-Kubernetes-Pf-Flowschema-Uid': '55b5c4db-e1d7-4305-b1f6-30bba1052339', 'X-Kubernetes-Pf-Prioritylevel-Uid': 'c9b3122f-0115-46db-b02e-4123ea22dbdf', 'Date': 'Thu, 12 Jan 2023 05:05:44 GMT', 'Content-Length': '363'})
HTTP response body: {"kind":"Status","apiVersion":"v1","metadata":{},"status":"Failure","message":"pods is forbidden: User \"system:serviceaccount:onap:onap-dcae-datalake-admin-ui-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-12 05:05:55,228 - INFO - Checking if dcae-datalake-feeder is ready
2023-01-12 05:05:55,231 - ERROR - Exception when calling list_namespaced_pod: (403)
Reason: Forbidden
HTTP response headers: HTTPHeaderDict({'Audit-Id': '390111a5-866a-46c1-baf1-fc543d6726e2', 'Cache-Control': 'no-cache, private', 'Content-Type': 'application/json', 'X-Content-Type-Options': 'nosniff', 'X-Kubernetes-Pf-Flowschema-Uid': '55b5c4db-e1d7-4305-b1f6-30bba1052339', 'X-Kubernetes-Pf-Prioritylevel-Uid': 'c9b3122f-0115-46db-b02e-4123ea22dbdf', 'Date': 'Thu, 12 Jan 2023 05:05:55 GMT', 'Content-Length': '363'})
HTTP response body: {"kind":"Status","apiVersion":"v1","metadata":{},"status":"Failure","message":"pods is forbidden: User \"system:serviceaccount:onap:onap-dcae-datalake-admin-ui-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-12 05:06:05,241 - INFO - Checking if dcae-datalake-feeder is ready
2023-01-12 05:06:05,245 - ERROR - Exception when calling list_namespaced_pod: (403)
Reason: Forbidden
HTTP response headers: HTTPHeaderDict({'Audit-Id': 'a79f0bf2-b893-48a3-88fb-fe52aef32df8', 'Cache-Control': 'no-cache, private', 'Content-Type': 'application/json', 'X-Content-Type-Options': 'nosniff', 'X-Kubernetes-Pf-Flowschema-Uid': '55b5c4db-e1d7-4305-b1f6-30bba1052339', 'X-Kubernetes-Pf-Prioritylevel-Uid': 'c9b3122f-0115-46db-b02e-4123ea22dbdf', 'Date': 'Thu, 12 Jan 2023 05:06:05 GMT', 'Content-Length': '363'})
HTTP response body: {"kind":"Status","apiVersion":"v1","metadata":{},"status":"Failure","message":"pods is forbidden: User \"system:serviceaccount:onap:onap-dcae-datalake-admin-ui-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-12 05:06:14,254 - INFO - Checking if dcae-datalake-feeder is ready
2023-01-12 05:06:21,708 - INFO - Deployment onap-dcae-datalake-feeder is NOT ready
2023-01-12 05:06:31,816 - INFO - Checking if dcae-datalake-feeder is ready
2023-01-12 05:06:39,322 - INFO - Deployment onap-dcae-datalake-feeder is NOT ready
2023-01-12 05:06:44,423 - INFO - Checking if dcae-datalake-feeder is ready
2023-01-12 05:06:51,729 - INFO - Deployment onap-dcae-datalake-feeder is NOT ready
2023-01-12 05:07:00,817 - INFO - Checking if dcae-datalake-feeder is ready
2023-01-12 05:07:08,026 - INFO - Deployment onap-dcae-datalake-feeder is NOT ready
2023-01-12 05:07:15,120 - INFO - Checking if dcae-datalake-feeder is ready
2023-01-12 05:07:22,418 - INFO - Deployment onap-dcae-datalake-feeder is NOT ready
2023-01-12 05:07:30,516 - INFO - Checking if dcae-datalake-feeder is ready
2023-01-12 05:07:38,516 - INFO - Deployment onap-dcae-datalake-feeder is NOT ready
2023-01-12 05:07:47,616 - INFO - Checking if dcae-datalake-feeder is ready
2023-01-12 05:07:55,327 - INFO - Deployment onap-dcae-datalake-feeder is NOT ready
2023-01-12 05:08:02,421 - INFO - Checking if dcae-datalake-feeder is ready
2023-01-12 05:08:10,121 - INFO - Deployment onap-dcae-datalake-feeder is NOT ready
2023-01-12 05:08:20,220 - INFO - Checking if dcae-datalake-feeder is ready
2023-01-12 05:08:28,207 - INFO - Deployment onap-dcae-datalake-feeder is NOT ready
2023-01-12 05:08:38,220 - INFO - Checking if dcae-datalake-feeder is ready
2023-01-12 05:08:46,018 - INFO - Deployment onap-dcae-datalake-feeder is NOT ready
2023-01-12 05:08:55,116 - INFO - Checking if dcae-datalake-feeder is ready
2023-01-12 05:09:03,117 - INFO - Deployment onap-dcae-datalake-feeder is NOT ready
2023-01-12 05:09:10,217 - INFO - Checking if dcae-datalake-feeder is ready
2023-01-12 05:09:18,408 - INFO - Deployment onap-dcae-datalake-feeder is NOT ready
2023-01-12 05:09:25,416 - INFO - Checking if dcae-datalake-feeder is ready
2023-01-12 05:09:33,719 - INFO - Deployment onap-dcae-datalake-feeder is NOT ready
2023-01-12 05:09:41,816 - INFO - Checking if dcae-datalake-feeder is ready
2023-01-12 05:09:50,212 - INFO - Deployment onap-dcae-datalake-feeder is NOT ready
2023-01-12 05:09:58,316 - INFO - Checking if dcae-datalake-feeder is ready
2023-01-12 05:10:05,922 - INFO - Deployment onap-dcae-datalake-feeder is NOT ready
2023-01-12 05:10:16,017 - INFO - Checking if dcae-datalake-feeder is ready
2023-01-12 05:10:24,410 - INFO - Deployment onap-dcae-datalake-feeder is NOT ready
2023-01-12 05:10:32,424 - INFO - Checking if dcae-datalake-feeder is ready
2023-01-12 05:10:40,918 - INFO - Deployment onap-dcae-datalake-feeder is NOT ready
2023-01-12 05:10:47,016 - INFO - Checking if dcae-datalake-feeder is ready
2023-01-12 05:10:55,811 - INFO - Deployment onap-dcae-datalake-feeder is NOT ready
2023-01-12 05:11:01,824 - INFO - Checking if dcae-datalake-feeder is ready
2023-01-12 05:11:10,717 - INFO - Deployment onap-dcae-datalake-feeder is NOT ready
2023-01-12 05:11:18,820 - INFO - Checking if dcae-datalake-feeder is ready
2023-01-12 05:11:27,613 - INFO - Deployment onap-dcae-datalake-feeder is NOT ready
2023-01-12 05:11:32,720 - INFO - Checking if dcae-datalake-feeder is ready
2023-01-12 05:11:41,815 - INFO - Deployment onap-dcae-datalake-feeder is ready