Apr 09 13:17:46.730 - 1s    E clusteroperator/openshift-apiserver condition/Available status/False reason/APIServicesAvailable: apiservices.apiregistration.k8s.io/v1.apps.openshift.io: not available: failing or missing response from https://10.128.0.73:8443/apis/apps.openshift.io/v1: Get "https://10.128.0.73:8443/apis/apps.openshift.io/v1": context deadline exceeded (Client.Timeout exceeded while awaiting headers)
    Apr 09 13:18:01.727 - 1s    E clusteroperator/openshift-apiserver condition/Available status/False reason/APIServicesAvailable: apiservices.apiregistration.k8s.io/v1.build.openshift.io: not available: failing or missing response from https://10.128.0.73:8443/apis/build.openshift.io/v1: Get "https://10.128.0.73:8443/apis/build.openshift.io/v1": context deadline exceeded
    Apr 09 13:18:16.874 - 1s    E clusteroperator/openshift-apiserver condition/Available status/False reason/APIServicesAvailable: apiservices.apiregistration.k8s.io/v1.apps.openshift.io: not available: failing or missing response from https://10.129.0.50:8443/apis/apps.openshift.io/v1: Get "https://10.129.0.50:8443/apis/apps.openshift.io/v1": context deadline exceeded\nAPIServicesAvailable: apiservices.apiregistration.k8s.io/v1.project.openshift.io: not available: failing or missing response from https://10.128.0.73:8443/apis/project.openshift.io/v1: Get "https://10.128.0.73:8443/apis/project.openshift.io/v1": dial tcp 10.128.0.73:8443: i/o timeout
    Apr 09 13:25:10.247 - 25s   E clusteroperator/openshift-apiserver condition/Available status/False reason/APIServicesAvailable: "apps.openshift.io.v1" is not ready: 503 (the server is currently unable to handle the request)\nAPIServicesAvailable: "authorization.openshift.io.v1" is not ready: 503 (the server is currently unable to handle the request)\nAPIServicesAvailable: "build.openshift.io.v1" is not ready: 503 (the server is currently unable to handle the request)\nAPIServicesAvailable: "image.openshift.io.v1" is not ready: 503 (the server is currently unable to handle the request)\nAPIServicesAvailable: "project.openshift.io.v1" is not ready: 503 (the server is currently unable to handle the request)\nAPIServicesAvailable: "quota.openshift.io.v1" is not ready: 503 (the server is currently unable to handle the request)\nAPIServicesAvailable: "route.openshift.io.v1" is not ready: 503 (the server is currently unable to handle the request)\nAPIServicesAvailable: "security.openshift.io.v1" is not ready: 503 (the server is currently unable to handle the request)\nAPIServicesAvailable: "template.openshift.io.v1" is not ready: 503 (the server is currently unable to handle the request)
    Apr 09 13:31:25.504 - 1s    E clusteroperator/openshift-apiserver condition/Available status/False reason/APIServicesAvailable: apiservices.apiregistration.k8s.io/v1.apps.openshift.io: not available: failing or missing response from https://10.128.0.10:8443/apis/apps.openshift.io/v1: Get "https://10.128.0.10:8443/apis/apps.openshift.io/v1": context deadline exceeded
    Apr 09 13:31:45.328 - 1s    E clusteroperator/openshift-apiserver condition/Available status/False reason/APIServicesAvailable: apiservices.apiregistration.k8s.io/v1.build.openshift.io: not available: failing or missing response from https://10.130.0.14:8443/apis/build.openshift.io/v1: Get "https://10.130.0.14:8443/apis/build.openshift.io/v1": net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)

Mar 18 08:38:51.004 E clusteroperator/openshift-apiserver condition/Available status/False reason/APIServices_Error changed: APIServicesAvailable: "route.openshift.io.v1" is not ready: an attempt failed with statusCode = 503, err = the server is currently unable to handle the request
Mar 18 08:38:51.004 - 1s    E clusteroperator/openshift-apiserver condition/Available status/False reason/APIServicesAvailable: "route.openshift.io.v1" is not ready: an attempt failed with statusCode = 503, err = the server is currently unable to handle the request
Mar 18 08:38:52.710 - 1s    E disruption/oauth-api connection/new reason/DisruptionBegan disruption/oauth-api connection/new stopped responding to GET requests over new connections: error running request: 503 Service Unavailable: error trying to reach service: dial tcp 10.130.0.120:8443: connect: connection refused\n

Mar 18 08:38:59.405 E clusteroperator/openshift-apiserver condition/Available status/False reason/APIServices_Error changed: APIServicesAvailable: "template.openshift.io.v1" is not ready: an attempt failed with statusCode = 503, err = the server is currently unable to handle the request
Mar 18 08:38:59.405 - 3s    E clusteroperator/openshift-apiserver condition/Available status/False reason/APIServicesAvailable: "template.openshift.io.v1" is not ready: an attempt failed with statusCode = 503, err = the server is currently unable to handle the request
Mar 18 08:38:59.711 - 1s    E disruption/cache-openshift-api connection/reused reason/DisruptionBegan disruption/cache-openshift-api connection/reused stopped responding to GET requests over reused connections: error running request: 503 Service Unavailable: error trying to reach service: dial tcp 10.130.0.127:8443: connect: connection refused\n

Mar 18 08:38:51.004 - 1s    E clusteroperator/openshift-apiserver condition/Available status/False reason/APIServicesAvailable: "route.openshift.io.v1" is not ready: an attempt failed with statusCode = 503, err = the server is currently unable to handle the request
Mar 18 08:38:59.405 - 3s    E clusteroperator/openshift-apiserver condition/Available status/False reason/APIServicesAvailable: "template.openshift.io.v1" is not ready: an attempt failed with statusCode = 503, err = the server is currently unable to handle the request

Mar 17 20:46:36.143 E clusteroperator/openshift-apiserver condition/Available status/False reason/APIServices_Error changed: APIServicesAvailable: Get "https://172.30.0.1:443/apis/apiregistration.k8s.io/v1/apiservices/v1.apps.openshift.io": read tcp 10.129.0.21:39452->172.30.0.1:443: read: connection timed out
Mar 17 20:46:36.143 - 1s    E clusteroperator/openshift-apiserver condition/Available status/False reason/APIServicesAvailable: Get "https://172.30.0.1:443/apis/apiregistration.k8s.io/v1/apiservices/v1.apps.openshift.io": read tcp 10.129.0.21:39452->172.30.0.1:443: read: connection timed out
Mar 17 20:46:39.658 - 1s    E ns/openshift-console route/console disruption/ingress-to-console connection/reused reason/DisruptionBegan ns/openshift-console route/console disruption/ingress-to-console connection/reused stopped responding to GET requests over reused connections: Get "https://console-openshift-console.apps.ci-op-hbvhz2k5-92453.aws-2.ci.openshift.org/healthz": net/http: timeout awaiting response headers

Mar 17 20:49:59.885 E clusteroperator/openshift-apiserver condition/Available status/False reason/APIServices_Error changed: APIServicesAvailable: Get "https://172.30.0.1:443/apis/apiregistration.k8s.io/v1/apiservices/v1.security.openshift.io": read tcp 10.129.0.21:48606->172.30.0.1:443: read: connection timed out
Mar 17 20:49:59.885 - 76ms  E clusteroperator/openshift-apiserver condition/Available status/False reason/APIServicesAvailable: Get "https://172.30.0.1:443/apis/apiregistration.k8s.io/v1/apiservices/v1.security.openshift.io": read tcp 10.129.0.21:48606->172.30.0.1:443: read: connection timed out
Mar 17 20:50:00.611 E ns/openshift-e2e-loki pod/loki-promtail-d272z node/ip-10-0-128-249.us-east-2.compute.internal uid/96db1dd9-3fbd-428e-a5c0-1d35c6155eef container/oauth-proxy reason/TerminationStateCleared lastState.terminated was cleared on a pod (bug https://bugzilla.redhat.com/show_bug.cgi?id=1933760 or similar)

Mar 17 20:53:58.773 E clusteroperator/openshift-apiserver condition/Available status/False reason/APIServices_Error changed: APIServicesAvailable: "image.openshift.io.v1" is not ready: an attempt failed with statusCode = 503, err = the server is currently unable to handle the request
Mar 17 20:53:58.773 - 78ms  E clusteroperator/openshift-apiserver condition/Available status/False reason/APIServicesAvailable: "image.openshift.io.v1" is not ready: an attempt failed with statusCode = 503, err = the server is currently unable to handle the request
Mar 17 20:54:08.570 E clusteroperator/network condition/Degraded status/True reason/ApplyOperatorConfig changed: Error while updating operator configuration: could not apply (apps/v1, Kind=DaemonSet) openshift-multus/multus: failed to apply / update (apps/v1, Kind=DaemonSet) openshift-multus/multus: Patch "https://api-int.ci-op-hbvhz2k5-92453.aws-2.ci.openshift.org:6443/apis/apps/v1/namespaces/openshift-multus/daemonsets/multus?fieldManager=cluster-network-operator%2Foperconfig&force=true": read tcp 10.0.207.14:57108->10.0.137.144:6443: read: connection reset by peer

Mar 17 20:46:36.143 - 1s    E clusteroperator/openshift-apiserver condition/Available status/False reason/APIServicesAvailable: Get "https://172.30.0.1:443/apis/apiregistration.k8s.io/v1/apiservices/v1.apps.openshift.io": read tcp 10.129.0.21:39452->172.30.0.1:443: read: connection timed out
Mar 17 20:49:59.885 - 76ms  E clusteroperator/openshift-apiserver condition/Available status/False reason/APIServicesAvailable: Get "https://172.30.0.1:443/apis/apiregistration.k8s.io/v1/apiservices/v1.security.openshift.io": read tcp 10.129.0.21:48606->172.30.0.1:443: read: connection timed out
Mar 17 20:53:58.773 - 78ms  E clusteroperator/openshift-apiserver condition/Available status/False reason/APIServicesAvailable: "image.openshift.io.v1" is not ready: an attempt failed with statusCode = 503, err = the server is currently unable to handle the request

Mar 17 08:38:14.412 E clusteroperator/openshift-apiserver condition/Available status/False reason/APIServices_Error changed: APIServicesAvailable: "apps.openshift.io.v1" is not ready: an attempt failed with statusCode = 503, err = the server is currently unable to handle the request\nAPIServicesAvailable: "authorization.openshift.io.v1" is not ready: an attempt failed with statusCode = 503, err = the server is currently unable to handle the request\nAPIServicesAvailable: "build.openshift.io.v1" is not ready: an attempt failed with statusCode = 503, err = the server is currently unable to handle the request\nAPIServicesAvailable: "image.openshift.io.v1" is not ready: an attempt failed with statusCode = 500, err = an error on the server ("Internal Server Error: \"/apis/image.openshift.io/v1\": Post \"https://172.30.0.1:443/apis/authorization.k8s.io/v1/subjectaccessreviews?timeout=10s\": read tcp 10.128.0.9:41490->172.30.0.1:443: read: connection timed out") has prevented the request from succeeding
Mar 17 08:38:14.412 - 167ms E clusteroperator/openshift-apiserver condition/Available status/False reason/APIServicesAvailable: "apps.openshift.io.v1" is not ready: an attempt failed with statusCode = 503, err = the server is currently unable to handle the request\nAPIServicesAvailable: "authorization.openshift.io.v1" is not ready: an attempt failed with statusCode = 503, err = the server is currently unable to handle the request\nAPIServicesAvailable: "build.openshift.io.v1" is not ready: an attempt failed with statusCode = 503, err = the server is currently unable to handle the request\nAPIServicesAvailable: "image.openshift.io.v1" is not ready: an attempt failed with statusCode = 500, err = an error on the server ("Internal Server Error: \"/apis/image.openshift.io/v1\": Post \"https://172.30.0.1:443/apis/authorization.k8s.io/v1/subjectaccessreviews?timeout=10s\": read tcp 10.128.0.9:41490->172.30.0.1:443: read: connection timed out") has prevented the request from succeeding
Mar 17 08:38:14.668 E ns/openshift-image-registry pod/node-ca-mxf6v node/ip-10-0-176-207.ec2.internal uid/345d0019-41ec-400f-8ace-669229a15bb5 container/node-ca reason/TerminationStateCleared lastState.terminated was cleared on a pod (bug https://bugzilla.redhat.com/show_bug.cgi?id=1933760 or similar)

Mar 17 08:38:14.412 - 167ms E clusteroperator/openshift-apiserver condition/Available status/False reason/APIServicesAvailable: "apps.openshift.io.v1" is not ready: an attempt failed with statusCode = 503, err = the server is currently unable to handle the request\nAPIServicesAvailable: "authorization.openshift.io.v1" is not ready: an attempt failed with statusCode = 503, err = the server is currently unable to handle the request\nAPIServicesAvailable: "build.openshift.io.v1" is not ready: an attempt failed with statusCode = 503, err = the server is currently unable to handle the request\nAPIServicesAvailable: "image.openshift.io.v1" is not ready: an attempt failed with statusCode = 500, err = an error on the server ("Internal Server Error: \"/apis/image.openshift.io/v1\": Post \"https://172.30.0.1:443/apis/authorization.k8s.io/v1/subjectaccessreviews?timeout=10s\": read tcp 10.128.0.9:41490->172.30.0.1:443: read: connection timed out") has prevented the request from succeeding
1 tests failed during this blip (2023-03-17 08:38:14.412730497 +0000 UTC to 2023-03-17 08:38:14.412730497 +0000 UTC): [sig-arch][Feature:ClusterUpgrade] Cluster should remain functional during upgrade [Disruptive] [Serial]

Mar 14 11:33:38.403 E clusteroperator/openshift-apiserver condition/Available status/False reason/APIServices_Error changed: APIServicesAvailable: Get "https://172.30.0.1:443/apis/apiregistration.k8s.io/v1/apiservices/v1.apps.openshift.io": read tcp 10.128.0.22:44276->172.30.0.1:443: read: connection timed out
Mar 14 11:33:38.403 - 4s    E clusteroperator/openshift-apiserver condition/Available status/False reason/APIServicesAvailable: Get "https://172.30.0.1:443/apis/apiregistration.k8s.io/v1/apiservices/v1.apps.openshift.io": read tcp 10.128.0.22:44276->172.30.0.1:443: read: connection timed out
Mar 14 11:33:48.791 E clusteroperator/authentication condition/Available status/False reason/APIServices_Error changed: APIServicesAvailable: "oauth.openshift.io.v1" is not ready: an attempt failed with statusCode = 503, err = the server is currently unable to handle the request\nAPIServicesAvailable: "user.openshift.io.v1" is not ready: an attempt failed with statusCode = 503, err = the server is currently unable to handle the request

Mar 14 11:33:38.403 - 4s    E clusteroperator/openshift-apiserver condition/Available status/False reason/APIServicesAvailable: Get "https://172.30.0.1:443/apis/apiregistration.k8s.io/v1/apiservices/v1.apps.openshift.io": read tcp 10.128.0.22:44276->172.30.0.1:443: read: connection timed out