Upgrading to version 1.0.30.0 IF1

Follow the instructions after this to upgrade the Integrated Analytics System to version 1.0.30.0 IF1.

Before you begin

Ensure that all the required preparation steps were performed as described in Preparation steps.

About this task

Only the system bundle is upgraded in version 1.0.30.0 IF1.

Procedure

Download or copy the Integrated Analytics System bundle to /localrepo.

Note: The upgrade bundle must be downloaded to the actual /localrepo partition on the node running the upgrade. GPFS is stopped during the upgrade, so if the bundle is downloaded to GPFS storage, the upgrade fails.
Run ap issues and resolve any of the issues that might impact the upgrade process.
Copy the tar.gz file from the downloaded location to a directory on node0101 with the same name as the version of the file name.
1. Create the new directory outside the container on node0101:
```
mkdir /localrepo/w.x.y.z_release
```
  where w.x.y.z is the release number. In this case, /localrepo defines the upgrade directory for the --upgrade-directory parameter that is used later.
  The directory name cannot start with release or iias prefix. Use the release number.
2. Move the upgrade package (tar.gz) file into this new directory:
```
mv package.tar.gz /localrepo/w.x.y.z_release
```
Start a session that continues if your connection is dropped.
```
tmux new-session -A -s apupgrade
```
If you get disconnected, the upgrade continues. To reconnect, issue the tmux attach -t apupgrade command.

Run the following command to upgrade the apupgrade:

 apupgrade--upgrade-apupgrade --upgrade-directory / [local_repository] --use-version w.x.y.z_release

For example:

apupgrade --upgrade-apupgrade --upgrade-directory /localrepo --use-version 1.0.28.0

Perform an upgrade pre-check.
The pre-check step is also run as part of the upgrade, but it is advised to run it before you start the actual upgrade so that the system health can be verified and fixed when needed.
```
apupgrade --preliminary-check --upgrade-directory [upgrade_directory] --use-version w.x.y.z_release
```
For example:
```
apupgrade --preliminary-check --upgrade-directory /localrepo --use-version 1.0.11.0_release
```
Run apupgrade --upgrade --upgrade-directory <upgrade_directory> --use-version <w.x.y.z>_release
Note:
- Do not use the --force-restart option as the upgrade process might fail with errors.
- If upgrading from a version earlier than v1.0.3.0, you must run this command twice.
Example:
```
apupgrade --upgrade --upgrade-directory /localrepo --use-version 1.0.11.0_release
```

Follow the status of the upgrade by reviewing the following logs:

/var/log/appliance/apupgrade/apupgrade.log
/var/log/appliance/apupgrade/apupgrade.log.tracelog
/var/log/appliance/apupgrade/apupgrade.1.0.x.x_release.status

Optional: Ensure that the Platform Manager and the system are up and running after all upgrades are complete.
1. The command ap state should return Ready.
2. The commands ap issues and ap issues -sw should be clear of problems. If not, fix any issues, and run the command apstart.

Results

In 1.0.30.0 IF1, the ap version -s container reflects the GPFS version as follows:

[root@sail62-t14-n1 ~]# ap version -s
Appliance software version is 1.0.30.0

All component versions are synchronized.

+-----------------------------+------------------------------+
| Component Name              | Version                      |
+-----------------------------+------------------------------+
| Appliance platform software | 1.0.30.0-20240820103140b118  |
| Interim Fixes               | IF1                          |
| apupgrade                   | 1.0.29.1-20240902010002b1712 |
| gpfs                        | 5.1.9.0-4                    |
| gpfsconfig                  | 1.0.30.0-20240815135616b1307 |
+-----------------------------+------------------------------+