1
0
mirror of https://github.com/openshift/openshift-docs.git synced 2026-02-05 21:46:22 +01:00
Files
openshift-docs/modules/update-upgrading-sro.adoc
2022-09-01 11:26:22 +00:00

65 lines
2.0 KiB
Plaintext

// Module included in the following assemblies:
//
// * updating/updating-clusters-sro.adoc
:_content-type: PROCEDURE
[id="updating-running-a-preflight-check-for-sro_{context}"]
= Running a preflight check for the Special Resource Operator
You can use the following example procedure to check the compatibility of a kernel module version before updating a cluster that includes the Special Resource Operator (SRO).
.Prerequisites
* You have a running {product-title} cluster.
* You installed the OpenShift CLI (`oc`).
* You are logged in to the OpenShift CLI as a user with `cluster-admin` privileges.
* You installed the SRO.
.Procedure
. Create the following preflight validation custom resource definition (CRD) and save the YAML as `prevalidation.yaml`.
+
[source,yaml]
----
apiVersion: sro.openshift.io/v1beta1
kind: PreflightValidation
metadata:
name: preflight
namespace: preflight
spec:
updateImage: quay.io/openshift-release-dev/ocp-release@sha256:f7f252c39b64601c8ac3de737a584ba4f6016b1f4b17801d726ca2fd15492878 <1>
----
<1> Specify the name of the update image here.
+
. Start the validation check by running the following command:
+
[source,terminal]
----
$ oc apply -f prevalidation.yaml
----
.Verification
* Check the status of the custom resource (CR) by running the following command:
+
[source,terminal]
----
$ oc describe preflightvalidations.sro.openshift.io/v1beta1 preflight
----
+
.Example output
The following is an example output in which `simple-oot` is a `SpecialResource` CR that is deployed on the cluster.
+
[source,terminal]
----
Status:
Cr Statuses:
Last Transition Time: 2022-08-02T08:48:45Z
Name: simple-oot
Status Reason: Verification successful, all driver-containers for the next kernel version are present
Verification Stage: Image
Verification Status: True
Events: <none>
----
+
The preflight check continues to run until all CRs are verified. You can repeat the preceding command to check the status. After all CRs are verified, you should delete the preflight CR.