Rolling Back the Upgrade Within 14.1.2

12.1.2 Rolling Back the Upgrade Within 14.1.2

If the Oracle Unified Directory Services Manager (OUDSM) upgrade fails, you can rollback to the previous OUDSM 14c container image, fix the issue, and then retry the upgrade.

You can also rollback if the upgrade was successful but you subsequently have functional issues.

To rollback the Oracle Unified Directory (OUDSM) installation perform the following steps:

Rollback the OUDSM deployment using the following command:
```
helm rollback <release_name> -n <namespace>
```
For example:
```
 helm rollback oudsm -n oudsmns
```
The output will look similar to the following:
```
Rollback was a success! Happy Helming!
```
The helm rollback will perform a rolling restart of the OUDSM pods.
Run the following command and make sure all the OUDSM pods are started:
```
kubectl get pods -n <namespace> -w
```
Note:
The -w flag allows you watch the status of the pods as they change.
For example:
```
kubectl get pods -n oudsmns -w
```
You can also tail the logs for the pods by running:
```
kubectl logs -f <pod> -n oudsmns
```

Once the pods are up and running, you can run the following command to show the previous OUDSM 14c container image is used by the pods:

kubectl describe pod <pod> -n <namespace> | grep image

For example:

kubectl describe pod oudsm-1 -n oudsmns | grep image

The output will look similar to the following:

...
Containers:
  oudsm-1:
    Container ID:   cri-o://6a35ef3a0721015aa99b2aaeebdc96528c8166db7bf36176f0b9665e43c10ded
    Image:          container-registry.oracle.com/middleware/oudsm_cpu:14.1.2.1.0-jdk17-ol8-<YYMMDD>
    Image ID:       container-registry.oracle.com/middleware/oudsm_cpu@sha256:2ae38d6bdca4c411d6b62289cf80563f611a1fdcbaf01632be7b4fa6a4169000

Verify the OUDSM deployment. See, Validating OUDSM URLs.