6.2 Performing the Upgrade
Upgrade the existing OAA, OARM installation to the latest version.
- On the installation host where you downloaded the installation files, navigate to the
$WORKDIR/oaaimages/oaa-install
directory:cd $WORKDIR/oaaimages/oaa-install
- Run the
installManagementContainer.sh
script as follows:./installManagementContainer.sh -t ./<oaa-image>.tar
This will upgrade the installed oaamgmt chart. As the upgrade progresses you will be prompted to answer various questions and perform certain tasks. The table below outlines some of the questions or tasks you may be asked to answer or perform:
Output Action Version check failed for podman, would you like to use docker instead? [Y/N]:
This message will appear if the installation host does not have podman installed as per the Installation Host Requirements. If you do not have podman at the required version then choose to use Docker by answering " Y
".Login into container-registry.oracle.com from browser and navigate to the location of each of the supporting images. On the right-hand side, select the Language from the drop-down menu and click Continue. Read the Oracle Standard Terms and Restrictions and click Accept to agree.
Finally, use 'podman login' to store the credentials locally. Login successful? [Y/N]:
Note:
If using Docker the above will saydocker login
.- Launch a browser and visit https://container-registry.oracle.com. Sign in with your credentials. Navigate to Database and then instantclient. On the right-hand side, select the Language from the drop-down menu and click Continue. Read the Oracle Standard Terms and Restrictions and click Accept to agree.
- Depending on whether you are using
podman or Docker use
podman login
ordocker login
to log intocontainer-registry.oracle.com
and enter your credentials when prompted:
or:podman login container-registry.oracle.com
docker login container-registry.oracle.com
Use 'podman login' to login into your private registry if you have not done so previously.Login successful? [Y/N]:
Note:
If using Docker the above will showdocker login
If your private Container Image Registry (CIR) where you store images requires a login, use podman login
ordocker login
to log into the CIR and enter your credentials when prompted:
or:podman login <container-registry.example.com>
docker login <container-registry.example.com>
Note:
The table above does not include an exhaustive list of all prompts you will see during the upgrade as most are self explanatory. - Once the Management Container installation is complete you will see output similar
to the
following:
Release "oaamgmt" has been upgraded. Happy Helming! NAME: oaamgmt LAST DEPLOYED: <DATE> NAMESPACE: oaans STATUS: deployed REVISION: 2 TEST SUITE: None Waiting 15 secs for OAA mgmt deployment to start... Executing 'kubectl get pods -n oaans | grep oaamgmt-oaa-mgmt- '... oaamgmt-oaa-mgmt-6f4c9cd56f-std6l 0/1 ContainerCreating 0 15s oaamgmt-oaa-mgmt-bf6d5c88-29lrn 1/1 Running 0 4h42m Waiting 15 secs for OAA mgmt rollout to complete... Executing 'kubectl get pods -n oaans | grep oaamgmt-oaa-mgmt- '... oaamgmt-oaa-mgmt-6f4c9cd56f-std6l 0/1 ContainerCreating 0 31s oaamgmt-oaa-mgmt-bf6d5c88-29lrn 1/1 Running 0 4h42m Waiting 15 secs for OAA mgmt rollout to complete... Executing 'kubectl get pods -n oaans | grep oaamgmt-oaa-mgmt- '... oaamgmt-oaa-mgmt-6f4c9cd56f-std6l 1/1 Running 0 46s oaamgmt-oaa-mgmt-bf6d5c88-29lrn 1/1 Terminating 0 4h42m Waiting 15 secs for OAA mgmt rollout to complete... Executing 'kubectl get pods -n oaans | grep oaamgmt-oaa-mgmt- '... oaamgmt-oaa-mgmt-6f4c9cd56f-std6l 1/1 Running 0 61s oaamgmt-oaa-mgmt-bf6d5c88-29lrn 1/1 Terminating 0 4h43m Waiting 15 secs for OAA mgmt rollout to complete... Executing 'kubectl get pods -n oaans | grep oaamgmt-oaa-mgmt- '... oaamgmt-oaa-mgmt-6f4c9cd56f-std6l 1/1 Running 0 76s oaamgmt-oaa-mgmt-bf6d5c88-29lrn 1/1 Terminating 0 4h43m Waiting 15 secs for OAA mgmt rollout to complete... File /u01/oracle/scripts/settings/installOAA.properties already exists, copying file to /u01/oracle/scripts/settings/installOAA.properties.<DATE> Copying OAA properties file to oaans/oaamgmt-oaa-mgmt-6f4c9cd56f-std6l:/u01/oracle/scripts/settings Use command 'kubectl exec -n oaans -ti oaamgmt-oaa-mgmt-6f4c9cd56f-std6l -- /bin/bash' to get a shell to the OAA mgmt pod. From pod shell, use command 'kubectl get pods' to verify communication with the cluster. Continue OAA installation from the OAA mgmt pod. OAA management installation complete.
- As per the output connect to the new OAA management pod, for
example:
This will take you into a bash shell inside the OAA management pod:kubectl exec -n oaans -ti oaamgmt-oaa-mgmt-6f4c9cd56f-std6l -- /bin/bash
[oracle@oaamgmt-oaa-mgmt-6f4c9cd56f-std6l /]$
- Inside the OAA management pod perform the
upgrade:
[oracle@oaamgmt-oaa-mgmt-6f4c9cd56f-std6l /]$ cd ~ [oracle@oaamgmt-oaa-mgmt-6f4c9cd56f-std6l ~]$ ./OAA.sh -f installOAA.properties
Note:
This will use the<NFS_CONFIG_PATH>/installOAA.properties
file. - Once the upgrade is complete you should see the upgrade is successful and the deployment details are printed to the screen.
- Run the following command to make sure all the pods are
running:
For example:kubectl get pods -n <namespace>
The output should look similar to the following:kubectl get pods -n oaans
NAME READY STATUS RESTARTS AGE oaainstall-customfactor-b5cf55778-rwg5l 1/1 Running 0 6m29s oaainstall-email-65dc5f679-6xtmd 1/1 Running 0 6m29s oaainstall-fido-5b46884c68-q9dxp 1/1 Running 0 6m29s oaainstall-oaa-65779f845b-b9g6c 1/1 Running 0 6m29s oaainstall-oaa-admin-ui-6689c9d4cd-jhfzx 1/1 Running 0 6m29s oaainstall-oaa-drss-9f68f4856-849x4 1/1 Running 0 6m29s oaainstall-oaa-kba-6b8c4cfb-x2xsm 1/1 Running 0 6m28s oaainstall-oaa-policy-7997547c98-8jl4n 1/1 Running 0 6m28s oaainstall-push-58b478c4f9-fx95n 1/1 Running 0 6m28s oaainstall-risk-68bf8b75b7-gg99q 1/1 Running 0 6m28s oaainstall-risk-cc-6f669d5c5c-sfhfx 1/1 Running 0 6m28s oaainstall-sms-786d684994-lktfz 1/1 Running 0 6m28s oaainstall-spui-94f6f5f9b-pmhc2 1/1 Running 0 6m28s oaainstall-totp-7759f4598d-8rqwv 1/1 Running 0 6m27s oaainstall-yotp-5f865df96-c5x52 1/1 Running 0 6m27s oaamgmt-oaa-mgmt-859d65684f-jq84f 1/1 Running 0 48m
- If you have enabled Oracle Universal Authenticator and the
oauth.applicationid
parameter in theinstallOAA.properties
is different from the default valuemyoaaprotectedapp1
, then follow the Update the oua.drss.oaa.group Property section in Post Installation Steps for Oracle Universal Authenticator.Note:
Do NOT follow the Run configureDRSS.sh To Create OUA Integration Agent Components section as this will have been done automatically for you during the upgrade. - If you have Push Notifications for Android configured, check that push notifications work successfully. See Accessing a Protected Application Using Android Push Notification.