Time Namespace Component RelatedObject Reason Message

default

apiserver

kube-system

TerminationGracefulTerminationFinished

All pending requests processed

default

apiserver

kube-system

TerminationStoppedServing

Server has stopped listening

kube-system

kas-connection-checker-685895c7c9-gxkjq

FailedScheduling

no nodes available to schedule pods

kube-system

kas-connection-checker-685895c7c9-gxkjq

FailedScheduling

no nodes available to schedule pods

kube-system

kas-connection-checker-685895c7c9-cmd4j

Scheduled

Successfully assigned kube-system/kas-connection-checker-685895c7c9-cmd4j to ip-10-0-137-242.us-east-2.compute.internal

kube-system

kas-connection-checker-685895c7c9-cmd4j

FailedScheduling

no nodes available to schedule pods

kube-system

kas-connection-checker-685895c7c9-cmd4j

FailedScheduling

no nodes available to schedule pods

default

apiserver

kube-system

TerminationMinimalShutdownDurationFinished

The minimal shutdown duration of 15s finished

default

apiserver

kube-system

TerminationStart

Received signal to terminate, becoming unready, but keeping serving

default

apiserver

kube-system

TerminationPreShutdownHooksFinished

All pre-shutdown hooks have been finished

kube-system

kas-connection-checker-685895c7c9-gxkjq

Scheduled

Successfully assigned kube-system/kas-connection-checker-685895c7c9-gxkjq to ip-10-0-137-242.us-east-2.compute.internal

kube-system

konnectivity-agent-s4j82

Scheduled

Successfully assigned kube-system/konnectivity-agent-s4j82 to ip-10-0-137-242.us-east-2.compute.internal

kube-system

kas-connection-checker-685895c7c9-9p9r4

FailedScheduling

no nodes available to schedule pods

kube-system

global-pull-secret-syncer-j4k5g

Scheduled

Successfully assigned kube-system/global-pull-secret-syncer-j4k5g to ip-10-0-137-242.us-east-2.compute.internal

kube-system

kas-connection-checker-685895c7c9-9p9r4

Scheduled

Successfully assigned kube-system/kas-connection-checker-685895c7c9-9p9r4 to ip-10-0-137-242.us-east-2.compute.internal

kube-system

kas-connection-checker-685895c7c9-9p9r4

FailedScheduling

no nodes available to schedule pods

kube-system

konnectivity-agent-hz4mk

Scheduled

Successfully assigned kube-system/konnectivity-agent-hz4mk to ip-10-0-131-7.us-east-2.compute.internal

kube-system

global-pull-secret-syncer-tvwzk

Scheduled

Successfully assigned kube-system/global-pull-secret-syncer-tvwzk to ip-10-0-141-76.us-east-2.compute.internal

kube-system

global-pull-secret-syncer-vgmh8

Scheduled

Successfully assigned kube-system/global-pull-secret-syncer-vgmh8 to ip-10-0-131-7.us-east-2.compute.internal

kube-system

konnectivity-agent-vlgrg

Scheduled

Successfully assigned kube-system/konnectivity-agent-vlgrg to ip-10-0-141-76.us-east-2.compute.internal

default

apiserver

openshift-kube-apiserver

KubeAPIReadyz

readyz=true

kube-system

default-scheduler

kube-scheduler

LeaderElection

kube-scheduler-fcd947f98-kdpqb_22aac0f7-e64a-4530-839d-9ef3f4bf62df became leader

kube-system

kube-controller-manager

kube-controller-manager

LeaderElection

kube-controller-manager-986b68ccd-75m2g_eb2b408d-8fda-4f13-9597-4df1e9bb0162 became leader

openshift-cluster-version

openshift-cluster-version

version

LeaderElection

cluster-version-operator-67596c75fc-x7jft_0024b25a-5888-4bd1-afa1-ae3ce5410ad9 became leader

openshift-cluster-version

openshift-cluster-version

version

LoadPayload

Loading payload version="4.22.20" image="registry.build02.ci.openshift.org/ci-op-s8cbjzxx/release@sha256:b94e4b85832b43dfa35785551effe5d16e122e3fa3ed277b6d765c945fe5ef14"

openshift-cluster-version

openshift-cluster-version

version

RetrievePayload

Retrieving and verifying payload version="4.22.20" image="registry.build02.ci.openshift.org/ci-op-s8cbjzxx/release@sha256:b94e4b85832b43dfa35785551effe5d16e122e3fa3ed277b6d765c945fe5ef14"

openshift-cluster-version

openshift-cluster-version

version

PayloadLoaded

Payload loaded version="4.22.20" image="registry.build02.ci.openshift.org/ci-op-s8cbjzxx/release@sha256:b94e4b85832b43dfa35785551effe5d16e122e3fa3ed277b6d765c945fe5ef14" architecture="Multi"

kube-system

deployment-controller

kas-connection-checker

ScalingReplicaSet

Scaled up replica set kas-connection-checker-685895c7c9 from 0 to 3

kube-system

replicaset-controller

kas-connection-checker-685895c7c9

SuccessfulCreate

Created pod: kas-connection-checker-685895c7c9-cmd4j

kube-system

replicaset-controller

kas-connection-checker-685895c7c9

SuccessfulCreate

Created pod: kas-connection-checker-685895c7c9-gxkjq

kube-system

replicaset-controller

kas-connection-checker-685895c7c9

SuccessfulCreate

Created pod: kas-connection-checker-685895c7c9-9p9r4

kube-system

kube-controller-manager

kube-controller-manager

LeaderElection

kube-controller-manager-568db59c4b-s6rn9_0cced28f-f6c0-4f74-b379-c99bda736032 became leader
(x7)

default

kubelet

ip-10-0-137-242.us-east-2.compute.internal

NodeHasSufficientPID

Node ip-10-0-137-242.us-east-2.compute.internal status is now: NodeHasSufficientPID
(x7)

default

kubelet

ip-10-0-137-242.us-east-2.compute.internal

NodeHasNoDiskPressure

Node ip-10-0-137-242.us-east-2.compute.internal status is now: NodeHasNoDiskPressure

kube-system

daemonset-controller

konnectivity-agent

SuccessfulCreate

Created pod: konnectivity-agent-s4j82

default

cloud-node-controller

ip-10-0-137-242.us-east-2.compute.internal

Synced

Node synced successfully

kube-system

daemonset-controller

global-pull-secret-syncer

SuccessfulCreate

Created pod: global-pull-secret-syncer-j4k5g
(x8)

default

kubelet

ip-10-0-137-242.us-east-2.compute.internal

NodeHasSufficientMemory

Node ip-10-0-137-242.us-east-2.compute.internal status is now: NodeHasSufficientMemory

kube-system

kubelet

kube-apiserver-proxy-ip-10-0-137-242.us-east-2.compute.internal

Pulling

Pulling image "quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:3a679d80eb36ca7db888d4fbd1fdf16b0997a7c7a107936396b7a57d8b199f4e"

kube-system

kubelet

konnectivity-agent-s4j82

Pulling

Pulling image "quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:ef3d8a5c5a290fbfb7b3688e9a224e9c47d9f3326f05a0f73577656437e3f406"

kube-system

kubelet

kube-apiserver-proxy-ip-10-0-137-242.us-east-2.compute.internal

Started

Container started

kube-system

kubelet

kube-apiserver-proxy-ip-10-0-137-242.us-east-2.compute.internal

Created

Container created

kube-system

kubelet

kube-apiserver-proxy-ip-10-0-137-242.us-east-2.compute.internal

Pulled

Successfully pulled image "quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:3a679d80eb36ca7db888d4fbd1fdf16b0997a7c7a107936396b7a57d8b199f4e" in 1.631s (1.631s including waiting). Image size: 294084393 bytes.

default

node-controller

ip-10-0-137-242.us-east-2.compute.internal

RegisteredNode

Node ip-10-0-137-242.us-east-2.compute.internal event: Registered Node ip-10-0-137-242.us-east-2.compute.internal in Controller

kube-system

kubelet

konnectivity-agent-s4j82

Started

Container started

kube-system

kubelet

konnectivity-agent-s4j82

Pulled

Successfully pulled image "quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:ef3d8a5c5a290fbfb7b3688e9a224e9c47d9f3326f05a0f73577656437e3f406" in 3.484s (3.484s including waiting). Image size: 276927292 bytes.
(x7)

default

kubelet

ip-10-0-141-76.us-east-2.compute.internal

NodeHasNoDiskPressure

Node ip-10-0-141-76.us-east-2.compute.internal status is now: NodeHasNoDiskPressure
(x7)

default

kubelet

ip-10-0-141-76.us-east-2.compute.internal

NodeHasSufficientPID

Node ip-10-0-141-76.us-east-2.compute.internal status is now: NodeHasSufficientPID

kube-system

daemonset-controller

global-pull-secret-syncer

SuccessfulCreate

Created pod: global-pull-secret-syncer-tvwzk

kube-system

kubelet

konnectivity-agent-s4j82

Created

Container created

kube-system

daemonset-controller

konnectivity-agent

SuccessfulCreate

Created pod: konnectivity-agent-vlgrg

default

cloud-node-controller

ip-10-0-141-76.us-east-2.compute.internal

Synced

Node synced successfully

kube-system

kubelet

kube-apiserver-proxy-ip-10-0-141-76.us-east-2.compute.internal

Pulling

Pulling image "quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:3a679d80eb36ca7db888d4fbd1fdf16b0997a7c7a107936396b7a57d8b199f4e"
(x8)

default

kubelet

ip-10-0-141-76.us-east-2.compute.internal

NodeHasSufficientMemory

Node ip-10-0-141-76.us-east-2.compute.internal status is now: NodeHasSufficientMemory

kube-system

kubelet

konnectivity-agent-vlgrg

Pulling

Pulling image "quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:ef3d8a5c5a290fbfb7b3688e9a224e9c47d9f3326f05a0f73577656437e3f406"

default

node-controller

ip-10-0-141-76.us-east-2.compute.internal

RegisteredNode

Node ip-10-0-141-76.us-east-2.compute.internal event: Registered Node ip-10-0-141-76.us-east-2.compute.internal in Controller

kube-system

kubelet

kube-apiserver-proxy-ip-10-0-141-76.us-east-2.compute.internal

Pulled

Successfully pulled image "quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:3a679d80eb36ca7db888d4fbd1fdf16b0997a7c7a107936396b7a57d8b199f4e" in 2.044s (2.044s including waiting). Image size: 294084393 bytes.

kube-system

kubelet

kube-apiserver-proxy-ip-10-0-141-76.us-east-2.compute.internal

Created

Container created

kube-system

kubelet

kube-apiserver-proxy-ip-10-0-141-76.us-east-2.compute.internal

Started

Container started

kube-system

kubelet

konnectivity-agent-vlgrg

Created

Container created

kube-system

kubelet

konnectivity-agent-vlgrg

Started

Container started

kube-system

kubelet

konnectivity-agent-vlgrg

Pulled

Successfully pulled image "quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:ef3d8a5c5a290fbfb7b3688e9a224e9c47d9f3326f05a0f73577656437e3f406" in 4.117s (4.117s including waiting). Image size: 276927292 bytes.
(x7)

default

kubelet

ip-10-0-131-7.us-east-2.compute.internal

NodeHasNoDiskPressure

Node ip-10-0-131-7.us-east-2.compute.internal status is now: NodeHasNoDiskPressure
(x7)

default

kubelet

ip-10-0-131-7.us-east-2.compute.internal

NodeHasSufficientPID

Node ip-10-0-131-7.us-east-2.compute.internal status is now: NodeHasSufficientPID

default

kubelet

ip-10-0-131-7.us-east-2.compute.internal

NodeAllocatableEnforced

Updated limits on system reserved cgroup /system.slice

default

kubelet

ip-10-0-131-7.us-east-2.compute.internal

NodeAllocatableEnforced

Updated Node Allocatable limit across pods
(x7)

default

kubelet

ip-10-0-131-7.us-east-2.compute.internal

NodeHasSufficientMemory

Node ip-10-0-131-7.us-east-2.compute.internal status is now: NodeHasSufficientMemory

kube-system

daemonset-controller

global-pull-secret-syncer

SuccessfulCreate

Created pod: global-pull-secret-syncer-vgmh8

kube-system

kubelet

kube-apiserver-proxy-ip-10-0-131-7.us-east-2.compute.internal

Pulling

Pulling image "quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:3a679d80eb36ca7db888d4fbd1fdf16b0997a7c7a107936396b7a57d8b199f4e"

kube-system

daemonset-controller

konnectivity-agent

SuccessfulCreate

Created pod: konnectivity-agent-hz4mk

default

cloud-node-controller

ip-10-0-131-7.us-east-2.compute.internal

Synced

Node synced successfully

kube-system

kubelet

konnectivity-agent-hz4mk

Pulling

Pulling image "quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:ef3d8a5c5a290fbfb7b3688e9a224e9c47d9f3326f05a0f73577656437e3f406"

kube-system

kubelet

kube-apiserver-proxy-ip-10-0-131-7.us-east-2.compute.internal

Created

Container created

default

node-controller

ip-10-0-131-7.us-east-2.compute.internal

RegisteredNode

Node ip-10-0-131-7.us-east-2.compute.internal event: Registered Node ip-10-0-131-7.us-east-2.compute.internal in Controller
(x6)

kube-system

kubelet

global-pull-secret-syncer-j4k5g

FailedMount

MountVolume.SetUp failed for volume "original-pull-secret" : object "kube-system"/"original-pull-secret" not registered

kube-system

kubelet

kube-apiserver-proxy-ip-10-0-131-7.us-east-2.compute.internal

Pulled

Successfully pulled image "quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:3a679d80eb36ca7db888d4fbd1fdf16b0997a7c7a107936396b7a57d8b199f4e" in 1.716s (1.716s including waiting). Image size: 294084393 bytes.

kube-system

kubelet

kube-apiserver-proxy-ip-10-0-131-7.us-east-2.compute.internal

Started

Container started

kube-system

kubelet

konnectivity-agent-hz4mk

Pulled

Successfully pulled image "quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:ef3d8a5c5a290fbfb7b3688e9a224e9c47d9f3326f05a0f73577656437e3f406" in 4.072s (4.072s including waiting). Image size: 276927292 bytes.

kube-system

kubelet

konnectivity-agent-hz4mk

Started

Container started

kube-system

kubelet

konnectivity-agent-hz4mk

Created

Container created
(x8)

default

ovnk-controlplane

ip-10-0-137-242.us-east-2.compute.internal

ErrorReconcilingNode

[k8s.ovn.org/node-chassis-id annotation not found for node ip-10-0-137-242.us-east-2.compute.internal, error getting gateway config for node ip-10-0-137-242.us-east-2.compute.internal: k8s.ovn.org/l3-gateway-config annotation not found for node "ip-10-0-137-242.us-east-2.compute.internal", failed to update chassis to local for local node ip-10-0-137-242.us-east-2.compute.internal, error: failed to parse node chassis-id for node - ip-10-0-137-242.us-east-2.compute.internal, error: k8s.ovn.org/node-chassis-id annotation not found for node ip-10-0-137-242.us-east-2.compute.internal]
(x6)

kube-system

kubelet

global-pull-secret-syncer-tvwzk

FailedMount

MountVolume.SetUp failed for volume "original-pull-secret" : object "kube-system"/"original-pull-secret" not registered
(x14)

kube-system

kubelet

global-pull-secret-syncer-j4k5g

NetworkNotReady

network is not ready: container runtime network not ready: NetworkReady=false reason:NetworkPluginNotReady message:Network plugin returns error: no CNI configuration file in /etc/kubernetes/cni/net.d/. Has your network provider started?

kube-system

kubelet

kas-connection-checker-685895c7c9-cmd4j

Pulled

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

kube-system

kubelet

kas-connection-checker-685895c7c9-9p9r4

Pulled

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

kube-system

multus

kas-connection-checker-685895c7c9-cmd4j

AddedInterface

Add eth0 [10.132.0.6/23] from ovn-kubernetes

kube-system

kubelet

kas-connection-checker-685895c7c9-gxkjq

Created

Container created

kube-system

kubelet

kas-connection-checker-685895c7c9-cmd4j

Created

Container created

kube-system

multus

kas-connection-checker-685895c7c9-9p9r4

AddedInterface

Add eth0 [10.132.0.17/23] from ovn-kubernetes
(x7)

default

ovnk-controlplane

ip-10-0-141-76.us-east-2.compute.internal

ErrorReconcilingNode

[k8s.ovn.org/node-chassis-id annotation not found for node ip-10-0-141-76.us-east-2.compute.internal, error getting gateway config for node ip-10-0-141-76.us-east-2.compute.internal: k8s.ovn.org/l3-gateway-config annotation not found for node "ip-10-0-141-76.us-east-2.compute.internal", failed to update chassis to local for local node ip-10-0-141-76.us-east-2.compute.internal, error: failed to parse node chassis-id for node - ip-10-0-141-76.us-east-2.compute.internal, error: k8s.ovn.org/node-chassis-id annotation not found for node ip-10-0-141-76.us-east-2.compute.internal]

kube-system

multus

kas-connection-checker-685895c7c9-gxkjq

AddedInterface

Add eth0 [10.132.0.7/23] from ovn-kubernetes

kube-system

kubelet

kas-connection-checker-685895c7c9-gxkjq

Pulled

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

kube-system

kubelet

kas-connection-checker-685895c7c9-9p9r4

Started

Container started

kube-system

kubelet

kas-connection-checker-685895c7c9-9p9r4

Created

Container created

kube-system

kubelet

kas-connection-checker-685895c7c9-cmd4j

Started

Container started

kube-system

kubelet

kas-connection-checker-685895c7c9-gxkjq

Started

Container started

kube-system

kubelet

global-pull-secret-syncer-j4k5g

Pulling

Pulling image "quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:fe8e89e6cbec3b50985683a4c052c0353f3b869fd22dae8191f84dbdcb591f87"
(x16)

kube-system

kubelet

global-pull-secret-syncer-tvwzk

NetworkNotReady

network is not ready: container runtime network not ready: NetworkReady=false reason:NetworkPluginNotReady message:Network plugin returns error: no CNI configuration file in /etc/kubernetes/cni/net.d/. Has your network provider started?

kube-system

multus

global-pull-secret-syncer-j4k5g

AddedInterface

Add eth0 [10.132.0.4/23] from ovn-kubernetes

kube-system

kubelet

global-pull-secret-syncer-j4k5g

Started

Container started

kube-system

kubelet

global-pull-secret-syncer-tvwzk

Pulling

Pulling image "quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:fe8e89e6cbec3b50985683a4c052c0353f3b869fd22dae8191f84dbdcb591f87"

kube-system

kubelet

global-pull-secret-syncer-j4k5g

Created

Container created

kube-system

kubelet

global-pull-secret-syncer-j4k5g

Pulled

Successfully pulled image "quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:fe8e89e6cbec3b50985683a4c052c0353f3b869fd22dae8191f84dbdcb591f87" in 4.796s (4.797s including waiting). Image size: 627364882 bytes.

kube-system

multus

global-pull-secret-syncer-tvwzk

AddedInterface

Add eth0 [10.133.0.5/23] from ovn-kubernetes

default

kubelet

ip-10-0-137-242.us-east-2.compute.internal

NodeHasSufficientPID

Node ip-10-0-137-242.us-east-2.compute.internal status is now: NodeHasSufficientPID

default

kubelet

ip-10-0-137-242.us-east-2.compute.internal

NodeHasNoDiskPressure

Node ip-10-0-137-242.us-east-2.compute.internal status is now: NodeHasNoDiskPressure

default

kubelet

ip-10-0-137-242.us-east-2.compute.internal

NodeHasSufficientMemory

Node ip-10-0-137-242.us-east-2.compute.internal status is now: NodeHasSufficientMemory

default

kubelet

ip-10-0-137-242.us-east-2.compute.internal

NodeAllocatableEnforced

Updated Node Allocatable limit across pods

default

kubelet

ip-10-0-137-242.us-east-2.compute.internal

NodeAllocatableEnforced

Updated limits on system reserved cgroup /system.slice

default

kubelet

ip-10-0-137-242.us-east-2.compute.internal

Starting

Starting kubelet.

default

kubelet

ip-10-0-141-76.us-east-2.compute.internal

Starting

Starting kubelet.

default

kubelet

ip-10-0-141-76.us-east-2.compute.internal

NodeHasNoDiskPressure

Node ip-10-0-141-76.us-east-2.compute.internal status is now: NodeHasNoDiskPressure

default

kubelet

ip-10-0-141-76.us-east-2.compute.internal

NodeAllocatableEnforced

Updated limits on system reserved cgroup /system.slice

default

kubelet

ip-10-0-141-76.us-east-2.compute.internal

NodeAllocatableEnforced

Updated Node Allocatable limit across pods

default

kubelet

ip-10-0-141-76.us-east-2.compute.internal

NodeHasSufficientMemory

Node ip-10-0-141-76.us-east-2.compute.internal status is now: NodeHasSufficientMemory

default

kubelet

ip-10-0-141-76.us-east-2.compute.internal

NodeHasSufficientPID

Node ip-10-0-141-76.us-east-2.compute.internal status is now: NodeHasSufficientPID

kube-system

kubelet

global-pull-secret-syncer-tvwzk

Pulled

Successfully pulled image "quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:fe8e89e6cbec3b50985683a4c052c0353f3b869fd22dae8191f84dbdcb591f87" in 4.898s (4.898s including waiting). Image size: 627364882 bytes.

kube-system

kubelet

global-pull-secret-syncer-tvwzk

Created

Container created

kube-system

kubelet

global-pull-secret-syncer-tvwzk

Started

Container started
(x7)

kube-system

kubelet

global-pull-secret-syncer-vgmh8

FailedMount

MountVolume.SetUp failed for volume "original-pull-secret" : object "kube-system"/"original-pull-secret" not registered
(x18)

kube-system

kubelet

global-pull-secret-syncer-vgmh8

NetworkNotReady

network is not ready: container runtime network not ready: NetworkReady=false reason:NetworkPluginNotReady message:Network plugin returns error: no CNI configuration file in /etc/kubernetes/cni/net.d/. Has your network provider started?

default

node-controller

ip-10-0-137-242.us-east-2.compute.internal

RegisteredNode

Node ip-10-0-137-242.us-east-2.compute.internal event: Registered Node ip-10-0-137-242.us-east-2.compute.internal in Controller

kube-system

kube-controller-manager

kube-controller-manager

LeaderElection

kube-controller-manager-b4c4ff48c-kkndm_09a071f5-90b6-4d21-804e-04eb01593d19 became leader

default

node-controller

ip-10-0-131-7.us-east-2.compute.internal

RegisteredNode

Node ip-10-0-131-7.us-east-2.compute.internal event: Registered Node ip-10-0-131-7.us-east-2.compute.internal in Controller

default

node-controller

ip-10-0-141-76.us-east-2.compute.internal

RegisteredNode

Node ip-10-0-141-76.us-east-2.compute.internal event: Registered Node ip-10-0-141-76.us-east-2.compute.internal in Controller

kube-system

node-controller

kube-apiserver-proxy-ip-10-0-131-7.us-east-2.compute.internal

NodeNotReady

Node is not ready

kube-system

node-controller

konnectivity-agent-hz4mk

NodeNotReady

Node is not ready
(x8)

default

ovnk-controlplane

ip-10-0-131-7.us-east-2.compute.internal

ErrorReconcilingNode

[k8s.ovn.org/node-chassis-id annotation not found for node ip-10-0-131-7.us-east-2.compute.internal, error getting gateway config for node ip-10-0-131-7.us-east-2.compute.internal: k8s.ovn.org/l3-gateway-config annotation not found for node "ip-10-0-131-7.us-east-2.compute.internal", failed to update chassis to local for local node ip-10-0-131-7.us-east-2.compute.internal, error: failed to parse node chassis-id for node - ip-10-0-131-7.us-east-2.compute.internal, error: k8s.ovn.org/node-chassis-id annotation not found for node ip-10-0-131-7.us-east-2.compute.internal]

default

kubelet

ip-10-0-131-7.us-east-2.compute.internal

NodeReady

Node ip-10-0-131-7.us-east-2.compute.internal status is now: NodeReady

kube-system

multus

global-pull-secret-syncer-vgmh8

AddedInterface

Add eth0 [10.134.0.4/23] from ovn-kubernetes

kube-system

kubelet

global-pull-secret-syncer-vgmh8

Pulling

Pulling image "quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:fe8e89e6cbec3b50985683a4c052c0353f3b869fd22dae8191f84dbdcb591f87"

kube-system

kubelet

global-pull-secret-syncer-vgmh8

Pulled

Successfully pulled image "quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:fe8e89e6cbec3b50985683a4c052c0353f3b869fd22dae8191f84dbdcb591f87" in 4.555s (4.555s including waiting). Image size: 627364882 bytes.

kube-system

kubelet

global-pull-secret-syncer-vgmh8

Created

Container created

default

kubelet

ip-10-0-131-7.us-east-2.compute.internal

Starting

Starting kubelet.

kube-system

kubelet

global-pull-secret-syncer-vgmh8

Started

Container started

default

kubelet

ip-10-0-131-7.us-east-2.compute.internal

NodeAllocatableEnforced

Updated Node Allocatable limit across pods

default

kubelet

ip-10-0-131-7.us-east-2.compute.internal

NodeAllocatableEnforced

Updated limits on system reserved cgroup /system.slice

default

kubelet

ip-10-0-131-7.us-east-2.compute.internal

NodeHasSufficientMemory

Node ip-10-0-131-7.us-east-2.compute.internal status is now: NodeHasSufficientMemory

default

kubelet

ip-10-0-131-7.us-east-2.compute.internal

NodeHasSufficientPID

Node ip-10-0-131-7.us-east-2.compute.internal status is now: NodeHasSufficientPID

default

kubelet

ip-10-0-131-7.us-east-2.compute.internal

NodeHasNoDiskPressure

Node ip-10-0-131-7.us-east-2.compute.internal status is now: NodeHasNoDiskPressure

kube-system

cert-manager-cainjector-5c57bbd4fc-jvdw7_acec2d0b-898d-408e-9bcb-1a15b74cf32a

cert-manager-cainjector-leader-election

LeaderElection

cert-manager-cainjector-5c57bbd4fc-jvdw7_acec2d0b-898d-408e-9bcb-1a15b74cf32a became leader

kube-system

cert-manager-leader-election

cert-manager-controller

LeaderElection

cert-manager-597b95cb84-ftl7m-external-cert-manager-controller became leader
(x2)

kube-system

kubelet

kube-apiserver-proxy-ip-10-0-141-76.us-east-2.compute.internal

Unhealthy

Liveness probe failed: Get "https://172.20.0.1:6443/version": context deadline exceeded