Rolling Back the 14c Upgrade to 12c

13.2.2 Rolling Back the 14c Upgrade to 12c

If the Oracle Unified Directory (OUD) 14c upgrade fails, you can rollback to OUD 12c, 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 (OUD) installation perform the following steps:

Run the following command to find the name of the StatefulSet:
```
kubectl get statefulsets -n <namespace>
```
For example:
```
kubectl get statefulsets -n oudns
```
The output will look similar to the following:
```
NAME        READY   AGE
oud-ds-rs   3/3     54m
```
Run the following commands to scale the replicas of the StatefulSet to 0. This ensures all pods are terminated gracefully:
```
kubectl scale statefulset <name> --replicas=0 -n <namespace>
```
For example:
```
kubectl scale statefulset oud-ds-rs --replicas=0 -n oudns
```
The output will look similar to the following:
```
statefulset.apps/oud-ds-rs scaled
```
Run the following command and make sure all the OUD pods are terminated before proceeding:
```
kubectl get pods -n <namespace>
```
For example:
```
kubectl get pods -n oudns
```

Restore the backup of the OUD 12c persistent volume:

sudo cp -rp <persistent_volume>/oud_user_projects <persistent_volume>/oud_user_projects_bkp14c

sudo rm -rf <persistent_volume>/oud_user_projects

sudo cp -rp <persistent_volume>/oud_user_projects_bkp12c <persistent_volume>/oud_user_projects

For example:

sudo cp -rp /nfs_volumes/oudpv/oud_user_projects /nfs_volumes/oudpv/oud_user_projects_bkp14c

sudo rm -rf /nfs_volumes/oudpv/oud_user_projects

sudo cp -rp /nfs_volumes/oudpv/oud_user_projects_bkp12c /nfs_volumes/oudpv/oud_user_projects/oud_user_projects

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

Run the following command to check the pods are now using the previous image:

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

For example:

kubectl describe pod oud-ds-rs-0 -n oudns | grep image

The output will look similar to the following:

...
Containers:
  oud-ds-rs:
    Container ID:   cri-o://6a35ef3a0721015aa99b2aaeebdc96528c8166db7bf36176f0b9665e43c10ded
    Image:          container-registry.oracle.com/middleware/oud_cpu:12.2.1.2.4-jdk8-ol8-<YYMMDD>
    Image ID:       container-registry.oracle.com/middleware/oud_cpu@sha256:2ae38d6bdca4c411d6b62289cf80563f611a1fdcbaf01632be7b4fa6a4169000

Verify the OUD deployment where applicable: