Troubleshoot Operator Installation¶
Introduction¶
OpenShift Operators are installed through OLM objects such as Subscriptions, InstallPlans, OperatorGroups, and ClusterServiceVersions. Installation issues usually appear in those objects before they appear in application pods.
Why This Matters¶
OpenShift administration relies on operators and cluster-scoped resources. A bad change can affect many projects, so inspect status and events before applying fixes.
Practical Examples¶
oc get subscription -n openshift-operators
oc get installplan -n openshift-operators
oc get csv -n openshift-operators
oc describe subscription example-operator -n openshift-operators
Example output:
NAME PACKAGE SOURCE CHANNEL
example-operator example-operator redhat-operators stable
NAME DISPLAY VERSION REPLACES PHASE
example-operator.v1.2.3 Example Operator 1.2.3 Succeeded
Verification¶
oc get csv -n openshift-operators
oc describe installplan -n openshift-operators
oc get events -n openshift-operators
Troubleshooting¶
Read the operator message, check the namespace where the component runs, inspect related events, and confirm whether the condition is Available, Progressing, or Degraded.
Common Mistakes¶
- Installing an operator into a namespace with the wrong OperatorGroup.
- Leaving manual InstallPlans unapproved.
- Checking only the operand and ignoring CSV phase.
Quick Checklist¶
- Confirm the active project.
- Inspect the exact object named in the error.
- Read recent events.
- Apply one focused fix.
- Verify status after the change.
Related Guides¶
Summary¶
Troubleshoot Operator Installation is an administration task that should be driven by cluster status, operator conditions, and component logs instead of broad restarts.