$ oc patch clusterversionoperator/cluster --type=merge --patch '{"spec":{"operatorLogLevel":"<log_level>"}}'
If your cluster update fails, you can examine cluster data to troubleshoot the failure.
To gather data from your cluster, including log data, use the oc adm must-gather command. See Gathering data about your cluster.
|
Changing the CVO log level is a Technology Preview feature only. Technology Preview features are not supported with Red Hat production service level agreements (SLAs) and might not be functionally complete. Red Hat does not recommend using them in production. These features provide early access to upcoming product features, enabling customers to test functionality and provide feedback during the development process. For more information about the support scope of Red Hat Technology Preview features, see Technology Preview Features Support Scope. |
The Cluster Version Operator (CVO) log level verbosity can be changed by the cluster administrator. There are four log levels.
Normal - The default log level. Contains working log information. Used when everything is fine. Provides helpful notices for auditing or common operations.
Debug - Used when something goes wrong. Expect a higher quantity of notices.
Trace - Used to diagnose errors.
TraceAll - Used to get the complete body content of the logs.
|
If |
You have access to the cluster as a user with the cluster-admin role.
You have installed the OpenShift CLI (oc).
You have the TechPreviewNoUpgrade feature set enabled.
Enter the following command into the CLI to change the log level.
$ oc patch clusterversionoperator/cluster --type=merge --patch '{"spec":{"operatorLogLevel":"<log_level>"}}'
clusterversionoperator.operator.openshift.io/cluster patched
The Cluster Version Operator (CVO) records updates made to a cluster, known as the ClusterVersion history. The entries can reveal correlation between changes in cluster behavior with potential triggers, although correlation does not imply causation.
|
The initial, minor, and z-stream version updates are stored by the ClusterVersion history. However, the ClusterVersion history has a size limit. If the limit is reached, the oldest z-stream updates in previous minor versions are pruned to accommodate the limit. |
You can view the ClusterVersion history by using the OKD web console or by using the OpenShift CLI (oc).
You can view the ClusterVersion history in the OKD web console.
You have access to the cluster as a user with the cluster-admin role.
You have access to the OKD web console.
From the web console, click Administration → Cluster Settings and review the contents of the Details tab.
oc)You can view the ClusterVersion history using the OpenShift CLI (oc).
You have access to the cluster as a user with the cluster-admin role.
You have installed the OpenShift CLI (oc).
View the cluster update history by entering the following command:
$ oc describe clusterversions/version
Desired:
Channels:
candidate-4.13
candidate-4.14
fast-4.13
fast-4.14
stable-4.13
Image: quay.io/openshift-release-dev/ocp-release@sha256:a148b19231e4634196717c3597001b7d0af91bf3a887c03c444f59d9582864f4
URL: https://access.redhat.com/errata/RHSA-2023:6130
Version: 4.13.19
History:
Completion Time: 2023-11-07T20:26:04Z
Image: quay.io/openshift-release-dev/ocp-release@sha256:a148b19231e4634196717c3597001b7d0af91bf3a887c03c444f59d9582864f4
Started Time: 2023-11-07T19:11:36Z
State: Completed
Verified: true
Version: 4.13.19
Completion Time: 2023-10-04T18:53:29Z
Image: quay.io/openshift-release-dev/ocp-release@sha256:eac141144d2ecd6cf27d24efe9209358ba516da22becc5f0abc199d25a9cfcec
Started Time: 2023-10-04T17:26:31Z
State: Completed
Verified: true
Version: 4.13.13
Completion Time: 2023-09-26T14:21:43Z
Image: quay.io/openshift-release-dev/ocp-release@sha256:371328736411972e9640a9b24a07be0af16880863e1c1ab8b013f9984b4ef727
Started Time: 2023-09-26T14:02:33Z
State: Completed
Verified: false
Version: 4.13.12
Observed Generation: 4
Version Hash: CMLl3sLq-EA=
Events: <none>