Recovering after a completed rollback

When the ProductRelease phase shows RollbackCompleted, the operator has rolled back all modified components to the last known good Helm revision. The cluster is consistent, but the installation or upgrade didn’t apply.

Important: Do not reattempt the installation or upgrade until you identify and fix the root cause. Reattempting without resolving the issue will cause the same failure and trigger another rollback.

Review the operator logs for the specific component that triggered the rollback.

kubectl logs -l app.kubernetes.io/name=iqstudio-operator \
  -n iqstudio-operator --since=30m

Check recent cluster events for any resource-level errors.

kubectl get events -A --sort-by='.lastTimestamp' | tail -30

Describe pods that did not reach the Running state.
```
kubectl describe pod <pod-name> -n <namespace>
```
Review the revision history to confirm what the operator rolled back to.
```
kubectl get productrelease <name> -n iqstudio-operator \
  -o jsonpath='{.status.history}' | python3 -m json.tool
```
Note: After resolving the root cause, delete the ProductRelease resource, correct the configuration or environment as required, and re-apply.

Delete the existing ProductRelease resource.

kubectl delete productrelease <name> -n iqstudio-operator

Correct the issue identified in the logs. For example, fix registry credentials, adjust resource requests, or resolve a storage class conflict.
Rerun the installer if the installation fails.

Important: If the installation fails, do not manually apply the CR YAML included in the package.

Rerun the installation script with the required configuration file. The installer generates and applies a temporary product release CR YAML based on your environment values. It skips completed steps based on the installation status and regenerates the required manifests.

Monitor the phase until it returns to Ready.

kubectl get productrelease -n iqstudio-operator -w