Time Namespace Component RelatedObject Reason Message

openshift-ingress

router-default-5864f9dbcc-9vf2j

Scheduled

Successfully assigned openshift-ingress/router-default-5864f9dbcc-9vf2j to ip-10-0-129-207.us-west-1.compute.internal

openshift-ingress

data-science-gateway-data-science-gateway-class-557c4f746fzsbh2

Scheduled

Successfully assigned openshift-ingress/data-science-gateway-data-science-gateway-class-557c4f746fzsbh2 to ip-10-0-128-219.us-west-1.compute.internal

openshift-ingress

openshift-ai-inference-openshift-ai-inference-564f56d49f-xct5q

Scheduled

Successfully assigned openshift-ingress/openshift-ai-inference-openshift-ai-inference-564f56d49f-xct5q to ip-10-0-128-219.us-west-1.compute.internal

openshift-ingress

router-default-5864f9dbcc-9vf2j

FailedScheduling

no nodes available to schedule pods

openshift-ingress

maas-default-gateway-openshift-default-746ff8f49f-plmnh

Scheduled

Successfully assigned openshift-ingress/maas-default-gateway-openshift-default-746ff8f49f-plmnh to ip-10-0-128-219.us-west-1.compute.internal

openshift-ingress

kube-auth-proxy-6cd4bcb5cf-slc4r

Scheduled

Successfully assigned openshift-ingress/kube-auth-proxy-6cd4bcb5cf-slc4r to ip-10-0-129-207.us-west-1.compute.internal

openshift-ingress

kube-auth-proxy-6cd4bcb5cf-kcthp

Scheduled

Successfully assigned openshift-ingress/kube-auth-proxy-6cd4bcb5cf-kcthp to ip-10-0-138-77.us-west-1.compute.internal

openshift-ingress

router-default-5864f9dbcc-9vf2j

FailedScheduling

no nodes available to schedule pods

openshift-ingress

istiod-openshift-gateway-7ddd9cfdc8-bf6lh

Scheduled

Successfully assigned openshift-ingress/istiod-openshift-gateway-7ddd9cfdc8-bf6lh to ip-10-0-128-219.us-west-1.compute.internal

openshift-ingress

istiod-openshift-gateway-7876bfcb74-fsvvr

Scheduled

Successfully assigned openshift-ingress/istiod-openshift-gateway-7876bfcb74-fsvvr to ip-10-0-129-207.us-west-1.compute.internal

openshift-ingress

deployment-controller

router-default

ScalingReplicaSet

Scaled up replica set router-default-5864f9dbcc from 0 to 1

openshift-ingress

replicaset-controller

router-default-5864f9dbcc

SuccessfulCreate

Created pod: router-default-5864f9dbcc-9vf2j

openshift-ingress

service-controller

router-default

EnsuringLoadBalancer

Ensuring load balancer

openshift-ingress

service-controller

router-default

UnAvailableLoadBalancer

There are no available nodes for LoadBalancer

openshift-ingress

service-controller

router-default

EnsuredLoadBalancer

Ensured load balancer
(x3)

openshift-ingress

service-controller

router-default

UpdatedLoadBalancer

Updated load balancer with new hosts
(x5)

openshift-ingress

kubelet

router-default-5864f9dbcc-9vf2j

FailedMount

MountVolume.SetUp failed for volume "metrics-certs" : secret "router-metrics-certs-default" not found
(x5)

openshift-ingress

kubelet

router-default-5864f9dbcc-9vf2j

FailedMount

MountVolume.SetUp failed for volume "service-ca-bundle" : configmap references non-existent config key: service-ca.crt
(x4)

openshift-ingress

kubelet

router-default-5864f9dbcc-9vf2j

FailedMount

MountVolume.SetUp failed for volume "service-ca-bundle" : configmap references non-existent config key: service-ca.crt
(x4)

openshift-ingress

kubelet

router-default-5864f9dbcc-9vf2j

FailedMount

MountVolume.SetUp failed for volume "metrics-certs" : secret "router-metrics-certs-default" not found

openshift-ingress

kubelet

router-default-5864f9dbcc-9vf2j

Created

Container created

openshift-ingress

kubelet

router-default-5864f9dbcc-9vf2j

Started

Container started

openshift-ingress

kubelet

router-default-5864f9dbcc-9vf2j

Pulled

Container image "quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:3a679d80eb36ca7db888d4fbd1fdf16b0997a7c7a107936396b7a57d8b199f4e" already present on machine and can be accessed by the pod

openshift-ingress

multus

router-default-5864f9dbcc-9vf2j

AddedInterface

Add eth0 [10.133.0.13/23] from ovn-kubernetes

openshift-ingress

gateway_labeler_controller

maas-default-gateway

AddedLabel

Added label istio.io/rev=openshift-gateway to gateway maas-default-gateway

openshift-ingress

replicaset-controller

istiod-openshift-gateway-7876bfcb74

SuccessfulCreate

Created pod: istiod-openshift-gateway-7876bfcb74-fsvvr

openshift-ingress

deployment-controller

istiod-openshift-gateway

ScalingReplicaSet

Scaled up replica set istiod-openshift-gateway-7876bfcb74 from 0 to 1

openshift-ingress

kubelet

istiod-openshift-gateway-7876bfcb74-fsvvr

Pulling

Pulling image "registry.redhat.io/openshift-service-mesh/istio-pilot-rhel9@sha256:d5adf3101d4e14c710cd05afb3fa53498e3c5fb31a120f1bb007fba2e3b376f8"

openshift-ingress

multus

istiod-openshift-gateway-7876bfcb74-fsvvr

AddedInterface

Add eth0 [10.133.0.24/23] from ovn-kubernetes

openshift-ingress

kubelet

istiod-openshift-gateway-7876bfcb74-fsvvr

Started

Container started

openshift-ingress

kubelet

istiod-openshift-gateway-7876bfcb74-fsvvr

Created

Container created

openshift-ingress

kubelet

istiod-openshift-gateway-7876bfcb74-fsvvr

Pulled

Successfully pulled image "registry.redhat.io/openshift-service-mesh/istio-pilot-rhel9@sha256:d5adf3101d4e14c710cd05afb3fa53498e3c5fb31a120f1bb007fba2e3b376f8" in 3.184s (3.184s including waiting). Image size: 185476477 bytes.

openshift-ingress

kubelet

istiod-openshift-gateway-7876bfcb74-fsvvr

ProbeError

Readiness probe error: HTTP probe failed with statuscode: 503 body:

openshift-ingress

kubelet

istiod-openshift-gateway-7876bfcb74-fsvvr

Unhealthy

Readiness probe failed: HTTP probe failed with statuscode: 503

openshift-ingress

deployment-controller

openshift-ai-inference-openshift-ai-inference

ScalingReplicaSet

Scaled up replica set openshift-ai-inference-openshift-ai-inference-564f56d49f from 0 to 1

openshift-ingress

deployment-controller

maas-default-gateway-openshift-default

ScalingReplicaSet

Scaled up replica set maas-default-gateway-openshift-default-746ff8f49f from 0 to 1

openshift-ingress

replicaset-controller

maas-default-gateway-openshift-default-746ff8f49f

SuccessfulCreate

Created pod: maas-default-gateway-openshift-default-746ff8f49f-plmnh

openshift-ingress

replicaset-controller

openshift-ai-inference-openshift-ai-inference-564f56d49f

SuccessfulCreate

Created pod: openshift-ai-inference-openshift-ai-inference-564f56d49f-xct5q

openshift-ingress

service-controller

openshift-ai-inference-openshift-ai-inference

EnsuringLoadBalancer

Ensuring load balancer

openshift-ingress

multus

openshift-ai-inference-openshift-ai-inference-564f56d49f-xct5q

AddedInterface

Add eth0 [10.132.0.32/23] from ovn-kubernetes

openshift-ingress

kubelet

maas-default-gateway-openshift-default-746ff8f49f-plmnh

Pulling

Pulling image "registry.redhat.io/openshift-service-mesh/istio-proxyv2-rhel9@sha256:1fc05d17a76d31503f68c5bde3057750a2c575981535756112c06589f88c8c55"

openshift-ingress

multus

maas-default-gateway-openshift-default-746ff8f49f-plmnh

AddedInterface

Add eth0 [10.132.0.30/23] from ovn-kubernetes

openshift-ingress

kubelet

openshift-ai-inference-openshift-ai-inference-564f56d49f-xct5q

Pulling

Pulling image "registry.redhat.io/openshift-service-mesh/istio-proxyv2-rhel9@sha256:1fc05d17a76d31503f68c5bde3057750a2c575981535756112c06589f88c8c55"

openshift-ingress

service-controller

openshift-ai-inference-openshift-ai-inference

EnsuredLoadBalancer

Ensured load balancer

openshift-ingress

kubelet

maas-default-gateway-openshift-default-746ff8f49f-plmnh

Pulled

Successfully pulled image "registry.redhat.io/openshift-service-mesh/istio-proxyv2-rhel9@sha256:1fc05d17a76d31503f68c5bde3057750a2c575981535756112c06589f88c8c55" in 9.629s (9.629s including waiting). Image size: 183555333 bytes.

openshift-ingress

kubelet

maas-default-gateway-openshift-default-746ff8f49f-plmnh

Started

Container started

openshift-ingress

kubelet

maas-default-gateway-openshift-default-746ff8f49f-plmnh

Created

Container created

openshift-ingress

kubelet

openshift-ai-inference-openshift-ai-inference-564f56d49f-xct5q

Started

Container started

openshift-ingress

kubelet

openshift-ai-inference-openshift-ai-inference-564f56d49f-xct5q

Created

Container created

openshift-ingress

kubelet

openshift-ai-inference-openshift-ai-inference-564f56d49f-xct5q

Pulled

Successfully pulled image "registry.redhat.io/openshift-service-mesh/istio-proxyv2-rhel9@sha256:1fc05d17a76d31503f68c5bde3057750a2c575981535756112c06589f88c8c55" in 9.787s (9.787s including waiting). Image size: 183555333 bytes.

openshift-ingress

horizontal-pod-autoscaler

openshift-ai-inference-openshift-ai-inference

FailedComputeMetricsReplicas

invalid metrics (1 invalid out of 1), first error is: failed to get cpu resource metric value: failed to get cpu utilization: unable to get metrics for resource cpu: no metrics returned from resource metrics API

openshift-ingress

horizontal-pod-autoscaler

openshift-ai-inference-openshift-ai-inference

FailedGetResourceMetric

failed to get cpu utilization: unable to get metrics for resource cpu: no metrics returned from resource metrics API
(x2)

openshift-ingress

horizontal-pod-autoscaler

maas-default-gateway-openshift-default

FailedComputeMetricsReplicas

invalid metrics (1 invalid out of 1), first error is: failed to get cpu resource metric value: failed to get cpu utilization: unable to get metrics for resource cpu: no metrics returned from resource metrics API
(x2)

openshift-ingress

horizontal-pod-autoscaler

maas-default-gateway-openshift-default

FailedGetResourceMetric

failed to get cpu utilization: unable to get metrics for resource cpu: no metrics returned from resource metrics API

openshift-ingress

horizontal-pod-autoscaler

openshift-ai-inference-openshift-ai-inference

FailedComputeMetricsReplicas

invalid metrics (1 invalid out of 1), first error is: failed to get cpu resource metric value: failed to get cpu utilization: did not receive metrics for targeted pods (pods might be unready)

openshift-ingress

horizontal-pod-autoscaler

openshift-ai-inference-openshift-ai-inference

FailedGetResourceMetric

failed to get cpu utilization: did not receive metrics for targeted pods (pods might be unready)

openshift-ingress

replicaset-controller

kube-auth-proxy-6cd4bcb5cf

SuccessfulCreate

Created pod: kube-auth-proxy-6cd4bcb5cf-slc4r

openshift-ingress

deployment-controller

data-science-gateway-data-science-gateway-class

ScalingReplicaSet

Scaled up replica set data-science-gateway-data-science-gateway-class-557c4f746f from 0 to 1

openshift-ingress

deployment-controller

kube-auth-proxy

ScalingReplicaSet

Scaled up replica set kube-auth-proxy-6cd4bcb5cf from 0 to 2

openshift-ingress

replicaset-controller

kube-auth-proxy-6cd4bcb5cf

SuccessfulCreate

Created pod: kube-auth-proxy-6cd4bcb5cf-kcthp

openshift-ingress

replicaset-controller

data-science-gateway-data-science-gateway-class-557c4f746f

SuccessfulCreate

Created pod: data-science-gateway-data-science-gateway-class-557c4f746fzsbh2

openshift-ingress

kubelet

data-science-gateway-data-science-gateway-class-557c4f746fzsbh2

Created

Container created

openshift-ingress

multus

kube-auth-proxy-6cd4bcb5cf-kcthp

AddedInterface

Add eth0 [10.134.0.24/23] from ovn-kubernetes

openshift-ingress

kubelet

kube-auth-proxy-6cd4bcb5cf-kcthp

Pulling

Pulling image "quay.io/opendatahub/odh-kube-auth-proxy@sha256:d90930380151490d5516eeb95840eecc743e9005fc02733dec6fe79e1a00e035"

openshift-ingress

multus

kube-auth-proxy-6cd4bcb5cf-slc4r

AddedInterface

Add eth0 [10.133.0.26/23] from ovn-kubernetes

openshift-ingress

kubelet

data-science-gateway-data-science-gateway-class-557c4f746fzsbh2

Started

Container started

openshift-ingress

kubelet

kube-auth-proxy-6cd4bcb5cf-slc4r

Pulling

Pulling image "quay.io/opendatahub/odh-kube-auth-proxy@sha256:d90930380151490d5516eeb95840eecc743e9005fc02733dec6fe79e1a00e035"

openshift-ingress

kubelet

data-science-gateway-data-science-gateway-class-557c4f746fzsbh2

Pulled

Container image "registry.redhat.io/openshift-service-mesh/istio-proxyv2-rhel9@sha256:1fc05d17a76d31503f68c5bde3057750a2c575981535756112c06589f88c8c55" already present on machine and can be accessed by the pod

openshift-ingress

multus

data-science-gateway-data-science-gateway-class-557c4f746fzsbh2

AddedInterface

Add eth0 [10.132.0.41/23] from ovn-kubernetes

openshift-ingress

kubelet

kube-auth-proxy-6cd4bcb5cf-slc4r

Created

Container created

openshift-ingress

kubelet

kube-auth-proxy-6cd4bcb5cf-slc4r

Pulled

Successfully pulled image "quay.io/opendatahub/odh-kube-auth-proxy@sha256:d90930380151490d5516eeb95840eecc743e9005fc02733dec6fe79e1a00e035" in 2.579s (2.579s including waiting). Image size: 188904677 bytes.

openshift-ingress

kubelet

kube-auth-proxy-6cd4bcb5cf-kcthp

Pulled

Successfully pulled image "quay.io/opendatahub/odh-kube-auth-proxy@sha256:d90930380151490d5516eeb95840eecc743e9005fc02733dec6fe79e1a00e035" in 2.672s (2.672s including waiting). Image size: 188904677 bytes.

openshift-ingress

kubelet

kube-auth-proxy-6cd4bcb5cf-slc4r

Started

Container started

openshift-ingress

kubelet

kube-auth-proxy-6cd4bcb5cf-kcthp

Created

Container created

openshift-ingress

kubelet

kube-auth-proxy-6cd4bcb5cf-kcthp

Started

Container started

openshift-ingress

horizontal-pod-autoscaler

kube-auth-proxy

FailedGetResourceMetric

failed to get cpu utilization: unable to get metrics for resource cpu: no metrics returned from resource metrics API

openshift-ingress

horizontal-pod-autoscaler

kube-auth-proxy

FailedComputeMetricsReplicas

invalid metrics (1 invalid out of 1), first error is: failed to get cpu resource metric value: failed to get cpu utilization: unable to get metrics for resource cpu: no metrics returned from resource metrics API

openshift-ingress

horizontal-pod-autoscaler

data-science-gateway-data-science-gateway-class

FailedGetResourceMetric

failed to get cpu utilization: unable to get metrics for resource cpu: no metrics returned from resource metrics API

openshift-ingress

horizontal-pod-autoscaler

data-science-gateway-data-science-gateway-class

FailedComputeMetricsReplicas

invalid metrics (1 invalid out of 1), first error is: failed to get cpu resource metric value: failed to get cpu utilization: unable to get metrics for resource cpu: no metrics returned from resource metrics API

openshift-ingress

horizontal-pod-autoscaler

kube-auth-proxy

FailedGetResourceMetric

failed to get cpu utilization: did not receive metrics for targeted pods (pods might be unready)

openshift-ingress

horizontal-pod-autoscaler

kube-auth-proxy

FailedComputeMetricsReplicas

invalid metrics (1 invalid out of 1), first error is: failed to get cpu resource metric value: failed to get cpu utilization: did not receive metrics for targeted pods (pods might be unready)

openshift-ingress

horizontal-pod-autoscaler

data-science-gateway-data-science-gateway-class

FailedGetResourceMetric

failed to get cpu utilization: did not receive metrics for targeted pods (pods might be unready)

openshift-ingress

horizontal-pod-autoscaler

data-science-gateway-data-science-gateway-class

FailedComputeMetricsReplicas

invalid metrics (1 invalid out of 1), first error is: failed to get cpu resource metric value: failed to get cpu utilization: did not receive metrics for targeted pods (pods might be unready)

openshift-ingress

replicaset-controller

istiod-openshift-gateway-7ddd9cfdc8

SuccessfulCreate

Created pod: istiod-openshift-gateway-7ddd9cfdc8-bf6lh

openshift-ingress

deployment-controller

istiod-openshift-gateway

ScalingReplicaSet

Scaled up replica set istiod-openshift-gateway-7ddd9cfdc8 from 0 to 1

openshift-ingress

kubelet

istiod-openshift-gateway-7ddd9cfdc8-bf6lh

Pulling

Pulling image "registry.redhat.io/openshift-service-mesh/istio-pilot-rhel9@sha256:d5adf3101d4e14c710cd05afb3fa53498e3c5fb31a120f1bb007fba2e3b376f8"

openshift-ingress

multus

istiod-openshift-gateway-7ddd9cfdc8-bf6lh

AddedInterface

Add eth0 [10.132.0.45/23] from ovn-kubernetes

openshift-ingress

kubelet

istiod-openshift-gateway-7ddd9cfdc8-bf6lh

Created

Container created

openshift-ingress

kubelet

istiod-openshift-gateway-7ddd9cfdc8-bf6lh

Started

Container started

openshift-ingress

kubelet

istiod-openshift-gateway-7ddd9cfdc8-bf6lh

Pulled

Successfully pulled image "registry.redhat.io/openshift-service-mesh/istio-pilot-rhel9@sha256:d5adf3101d4e14c710cd05afb3fa53498e3c5fb31a120f1bb007fba2e3b376f8" in 3.1s (3.1s including waiting). Image size: 185476477 bytes.
(x2)

openshift-ingress

kubelet

istiod-openshift-gateway-7ddd9cfdc8-bf6lh

Unhealthy

Readiness probe failed: HTTP probe failed with statuscode: 503
(x2)

openshift-ingress

kubelet

istiod-openshift-gateway-7ddd9cfdc8-bf6lh

ProbeError

Readiness probe error: HTTP probe failed with statuscode: 503 body:

openshift-ingress

replicaset-controller

istiod-openshift-gateway-7876bfcb74

SuccessfulDelete

Deleted pod: istiod-openshift-gateway-7876bfcb74-fsvvr

openshift-ingress

kubelet

istiod-openshift-gateway-7876bfcb74-fsvvr

Killing

Stopping container discovery

openshift-ingress

deployment-controller

istiod-openshift-gateway

ScalingReplicaSet

Scaled down replica set istiod-openshift-gateway-7876bfcb74 from 1 to 0
(x3)

openshift-ingress

horizontal-pod-autoscaler

istiod-openshift-gateway

FailedGetResourceMetric

failed to get cpu utilization: unable to get metrics for resource cpu: no metrics returned from resource metrics API
(x3)

openshift-ingress

horizontal-pod-autoscaler

istiod-openshift-gateway

FailedComputeMetricsReplicas

invalid metrics (1 invalid out of 1), first error is: failed to get cpu resource metric value: failed to get cpu utilization: unable to get metrics for resource cpu: no metrics returned from resource metrics API
(x2)

openshift-ingress

horizontal-pod-autoscaler

istiod-openshift-gateway

FailedGetResourceMetric

failed to get cpu utilization: did not receive metrics for targeted pods (pods might be unready)
(x2)

openshift-ingress

horizontal-pod-autoscaler

istiod-openshift-gateway

FailedComputeMetricsReplicas

invalid metrics (1 invalid out of 1), first error is: failed to get cpu resource metric value: failed to get cpu utilization: did not receive metrics for targeted pods (pods might be unready)