Events in {product-title} are modeled based on events that happen to API objects in an {product-title} cluster. Events allow {product-title} to record information about real-world events in a resource-agnostic manner. They also allow developers and administrators to consume information about system components in a unified way.
You can get a list of events in a given project using the following command:
$ oc get events [-n <project>]
You can see events in your project from the web console from the Browse → Events page. Many other objects, such as pods and deployments, have their own Events tab as well, which shows events related to that object.
This section describes the events of {product-title}.
Name | Description |
---|---|
|
Failed pod configuration validation. |
Name | Description |
---|---|
|
Back-off restarting failed the container. |
|
Container created. |
|
Pull/Create/Start failed. |
|
Killing the container. |
|
Container started. |
|
Preempting other pods. |
|
Container runtime did not stop the pod within specified grace period. |
Name | Description |
---|---|
|
Container is unhealthy. |
Name | Description |
---|---|
|
Back off Ctr Start, image pull. |
|
The image’s NeverPull Policy is violated. |
|
Failed to pull the image. |
|
Failed to inspect the image. |
|
Successfully pulled the image or the container image is already present on the machine. |
|
Pulling the image. |
Name | Description |
---|---|
|
Free disk space failed. |
|
Invalid disk capacity. |
Name | Description |
---|---|
|
Volume mount failed. |
|
Host network not supported. |
|
Host/port conflict. |
|
Insufficient free CPU. |
|
Insufficient free memory. |
|
Kubelet setup failed. |
|
Undefined shaper. |
|
Node is not ready. |
|
Node is not schedulable. |
|
Node is ready. |
|
Node is schedulable. |
|
Node selector mismatch. |
|
Out of disk. |
|
Node rebooted. |
|
Starting kubelet. |
|
Failed to attach volume. |
|
Failed to detach volume. |
|
Failed to expand/reduce volume. |
|
Successfully expanded/reduced volume. |
|
Failed to expand/reduce file system. |
|
Successfully expanded/reduced file system. |
|
Failed to unmount volume. |
|
Failed to map a volume. |
|
Failed unmaped device. |
|
Volume is already mounted. |
|
Volume is successfully detached. |
|
Volume is successfully mounted. |
|
Volume is successfully unmounted. |
|
Container garbage collection failed. |
|
Image garbage collection failed. |
|
Failed to enforce System Reserved Cgroup limit. |
|
Enforced System Reserved Cgroup limit. |
|
Unsupported mount option. |
|
Pod sandbox changed. |
|
Failed to create pod sandbox. |
|
Failed pod sandbox status. |
Name | Description |
---|---|
|
Pod sync failed. |
Name | Description |
---|---|
|
There is an OOM (out of memory) situation on the cluster. |
Name | Description |
---|---|
|
Failed to stop a pod. |
|
Failed to create a pod contianer. |
|
Failed to make pod data directories. |
|
Network is not ready. |
|
Error creating: |
|
Created pod: |
|
Error deleting: |
|
Deleted pod: |
Name | Description |
---|---|
SelectorRequired |
Selector is required. |
|
Could not convert selector into a corresponding internal selector object. |
|
HPA was unable to compute the replica count. |
|
Unknown metric source type. |
|
HPA was able to successfully calculate a replica count. |
|
Failed to convert the given HPA. |
|
HPA controller was unable to get the target’s current scale. |
|
HPA controller was able to get the target’s current scale. |
|
Failed to compute desired number of replicas based on listed metrics. |
|
New size: |
|
New size: |
|
Failed to update status. |
Name | Description |
---|---|
|
Starting OpenShift-SDN. |
|
The pod’s network interface has been lost and the pod will be stopped. |
Name | Description |
---|---|
|
The service-port |
Name | Description |
---|---|
|
There are no persistent volumes available and no storage class is set. |
|
Volume size or class is different from what is requested in claim. |
|
Error creating recycler pod. |
|
Occurs when volume is recycled. |
|
Occurs when pod is recycled. |
|
Occurs when volume is deleted. |
|
Error when deleting the volume. |
|
Occurs when volume for the claim is provisioned either manually or via external software. |
|
Failed to provision volume. |
|
Error cleaning provisioned volume. |
|
Occurs when the volume is provisioned successfully. |
|
Delay binding until pod scheduling. |
Name | Description |
---|---|
|
Handler failed for pod start. |
|
Handler failed for pre-stop. |
|
Pre-stop hook unfinished. |
Name | Description |
---|---|
|
Failed to cancel deployment. |
|
Cancelled deployment. |
|
Created new replication controller. |
|
No available ingress IP to allocate to service. |
Name | Description |
---|---|
|
Failed to schedule pod: |
|
By |
|
Successfully assigned |
Name | Description |
---|---|
|
This daemon set is selecting all pods. A non-empty selector is required. |
|
Failed to place pod on |
|
Found failed daemon pod |
Name | Description |
---|---|
|
Error creating load balancer. |
|
Deleting load balancer. |
|
Ensuring load balancer. |
|
Ensured load balancer. |
|
There are no available nodes for |
|
Lists the new |
|
Lists the new IP address. For example, |
|
Lists external IP address. For example, |
|
Lists the new UID. For example, |
|
Lists the new |
|
Lists the new |
|
Updated load balancer with new hosts. |
|
Error updating load balancer with new hosts. |
|
Deleting load balancer. |
|
Error deleting load balancer. |
|
Deleted load balancer. |