Chapter 29. Events
29.1. Overview
Events in OpenShift Container Platform are modeled based on events that happen to API objects in an OpenShift Container Platform cluster. Events allow OpenShift Container Platform 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.
29.2. Viewing Events with the CLI
You can get a list of events in a given project using the following command:
$ oc get events [-n <project>]
29.3. Viewing Events in the Console
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.
29.4. Comprehensive List of Events
This section describes the events of OpenShift Container Platform.
Table 29.1. Configuration Events
| Name | Description |
|---|---|
|
| Failed pod configuration validation. |
Table 29.2. Container Events
| Name | Description |
|---|---|
|
| Back-off restarting failed the container. |
|
| Container created. |
|
| Pull/Create/Start failed. |
|
| Killing the container. |
|
| Container started. |
Table 29.3. Health Events
| Name | Description |
|---|---|
|
| Container is unhealthy. |
Table 29.4. Image Events
| 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. |
Table 29.5. Image Manager Events
| Name | Description |
|---|---|
|
| Free disk space failed. |
|
| Invalid disk capacity. |
Table 29.6. Node Events
| 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. |
Table 29.7. Pod Worker Events
| Name | Description |
|---|---|
|
| Pod sync failed. |
Table 29.8. System Events
| Name | Description |
|---|---|
|
| There is an OOM (out of memory) situation on the cluster. |
Where did the comment section go?
Red Hat's documentation publication system recently went through an upgrade to enable speedier, more mobile-friendly content. We decided to re-evaluate our commenting platform to ensure that it meets your expectations and serves as an optimal feedback mechanism. During this redesign, we invite your input on providing feedback on Red Hat documentation via the discussion platform.