Upgrading Ops Center Administrator by using the application installer

If you are running Ops Center Administrator v10.0.x or later, you can use the application installer to upgrade.

Verify the following:

There is a total of 60 GiB of temporary available space. This includes the following:
- 40 GiB under the Podman root directory (default directory: /var/lib/containers)
- 10 GiB under /var/tmp
- 10 GiB under /tmp
There are no backup or restore jobs running.
The Virtual Appliance Manager log level is set to INFO. Upgrading fails when the log level is set to DEBUG or TRACE.
When you change to a different network mode during upgrading, do the following:
- When you change the network mode to bridge mode, verify the following:
  IP forwarding and br_netfilter for the IP V4 network are installed on the operating system. For details, see Installing Ops Center Administrator with the application installer.
  
  The OS running firewalld (for example, RHEL 8 or later) is configured to allow communication between containers. For details, see Installing Ops Center Administrator with the application installer.
- When you change the network mode to host mode, verify the following:
  Required port numbers for host mode are not allocated to other programs installed on the same computer. For details, see Port requirements.

If you also want to upgrade the container runtime version, verify the following additional prerequisites:
Note: You can upgrade Podman (major or minor version) during the installation or upgrade process, or after installing Ops Center Administrator. However, if you are upgrading Podman from version 3.x to 4.x, we recommend that you do so during the Ops Center Administrator installation. This is because upgrading Podman from version 3.x to 4.x after installation requires creating a backup of the existing Ops Center Administrator instance, removing it along with the Podman upgrade, reinstalling Ops Center Administrator, and then restoring the backup.
- If the supported version of Podman is not installed in the environment, you must configure Yellowdog Updater, Modified (YUM) settings to install packages over a network. The application installer connects to the configured YUM repository and installs the required version of Podman. The packages related to Podman are located in the latest BaseOS and AppStream repositories.
  If you want to install or upgrade Podman yourself, you can run the following command:
```
yum install podman-required-version
```
  For example, to install Podman v3.3.x:
```
yum install podman-3.3.*
```
  The asterisk indicates to obtain and install the latest patch version available in the repository.
  
  Note: Downgrading the Podman version is not supported.
- If you install or upgrade Ops Center Administrator while suppressing the upgrade of Podman, the installation fails with the error - [Error] Failed to install Podman x.x.x from package repository. Confirm the network or repository server setting, and retry. Unlock the suppression and install or upgrade Ops Center Administrator again. After completing the installation, suppress the upgrade of Podman again.
- If you install Podman 3.3.x, or upgrade Podman from 3.3.x to any version, or run any Podman command on the server using Podman 3.3.x, a warning message Failed to decode the keys [<key1>, <key2>, ..., <keyN>] from "/usr/share/containers/containers.conf" may appear. Ignore this message because it does not affect Ops Center Administrator.
- If you cannot use YUM to install Podman because your management server is not connected to the network, you must get the Podman software from the OS media (ISO image or CD-ROM).
  For example, the minimum supported version of Podman 3.3.x is available with Red Hat Enterprise Linux and Oracle Linux version 8.5, and Podman 4.2.x is available with version 9.1. Therefore, regardless of the OS version that you are using, you must download the OS that includes the version of Podman that you want to use.
1. Download the Linux ISO image (for example, redhat 8.5 iso).
2. Mount the ISO image using the following command:
  mount /dev/cdrom /media
  
  For example: mount -o loop rhel-8.5-x86_64-dvd.iso /media
3. If the /etc/yum.repos.d directory contains an existing repo file, rename the file extension or delete it.
4. Create the yum repository file by running the following command:
  vim /etc/yum.repos.d/local.repo
5. Add the required definition lines as shown in the following examples, and then save and close the file:
  For Oracle Linux
```
[LocalRepo_BaseOS]name= LocalRepo_BaseOS
gpgcheck=0
enabled=1
baseurl=file:///media/BaseOS/
LocalRepo_AppStream]
name=LocalRepo_AppStream
gpgcheck=0
enabled=1
baseurl=file:///media/AppStream/
```
  For Red Hat Enterprise Linux
```
[LocalRepo_BaseOS]
name=LocalRepo_BaseOS
metadata_expire=-1
enabled=1
gpgcheck=0
baseurl=file:///media/BaseOS/
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-redhat-release
 
[LocalRepo_AppStream]
name=LocalRepo_AppStream
metadata_expire=-1
enabled=1
gpgcheck=0
baseurl=file:///media/AppStream/
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-redhat-release
```
6. Verify the required library by running the following command:
  yum repolist
7. Install podman by using the following command :
```
yum install podman-required-version
```
  For example, to install Podman v3.3.x:
```
yum install podman-3.3.*
```
During installation, the following files are created under /tmp. Delete them if they are no longer required:
- Application log
- Audit log
- Backup file
The installation log is created under /var/logs/rainier-install.

Note: When upgrading Ops Center Administrator, do not configure the noexec mount option for the file system including the /tmp and /var/tmp directories. To check whether the option is configured, run the mount command.

Either open an SSH connection to the VM or open the VMware console and press Alt+F2 to reach the console.
Log in using a root user or a normal user account. If you log in as a normal user, use the sudo command to complete the following procedure as the root user.
Copy the tar file ops-center-administrator-xx.tar.gz from the installation media to any folder in the Linux environment and extract it. Navigate to the extracted folder.
Navigate to the extracted folder and run the following command:
sudo ./install.sh.
Log in when prompted.
- When upgrading from Ops Center Administrator installed using the Ops Center preconfigured media or application installer:
  - User name: sysadmin
  - Password: Specify the current password. (default password: sysadmin)
- When upgrading from Ops Center Administrator installed using the stand-alone preconfigured media:
  - User name: service
  - Password: Specify the current password. (default password: Chang3Me!)

At the following prompts, enter y:

Older version exists. Do you want to upgrade? [y/n]:

At the following prompts, enter the corresponding number to change the network mode. Press Enter to keep the current mode.

Current network mode is "bridge". Do you want to change it?

1. bridge : (Current) Containers are isolated from the host's
            network namespace and communicate through the host's virtual
            bridge. This mode is suitable for most cases.

2. host   : Containers share the host's network namespace.
            Therefore, no IP forwarding is required. This mode is used 
		    when it is absolutely necessary to disable IP forwarding 
		   (net.ipv4.ip_forward=0).

Enter the number [current=1]:

If you want to register Ops Center Administrator with Ops Center Common Services during installation, enter y at the prompt:
```
Do you wish to configure Ops Center Common Services [y/n]:
```
Ops Center Administrator begins upgrading.
If you change the network mode to host mode, restart the OS after the upgrade completes.
Suppress the upgrade of Podman to avoid unintentionally upgrading to an unsupported version.

For example, you can use yum-plugin-versionlock or you can add the exclude parameter to the yum.conf file.

Troubleshooting the upgrade

If the installation fails, try the following:

Check and resolve any error messages and then retry the installation.
Verify that the Virtual Appliance Manager log level is set to INFO. Upgrading fails when the log level is set to DEBUG or TRACE.
Check your YUM settings and the host network to make sure that your system can connect to the YUM repository.
If you use a local YUM mirror repository server, confirm the HTTP server setting and whether the repository data gathered by the reposync command exists correctly.
Restart the Podman service, verify that the older version is running, and then retry the installation.
Check the Podman logs.
For more information on how to perform these actions, consult your container runtime documentation.
View the journal log entries to see whether there is additional error information by connecting to the host with a root user or a normal user account and running the following commands:
Note: If you log in as a normal user, use the sudo command to complete the following procedure as the root user.
- journalctl --no-pager
- journalctl --no-pager -u rainier
If an error message indicates a failure to create the data-app-manager container before the upgrade, perform the following procedure:
1. Remove and reinstall Ops Center Administrator.
2. Restore the settings using the rainier-backup-yyyymmdd-hhmmss.tar.gz file in /tmp. For details, see "Backing up and restoring system settings" in the Hitachi Ops Center Administrator User Guide.
If an error message indicates a failure to take over the JDK used in the container before the upgrade, perform the following procedure to install the newer version of Ops Center Administrator with the bundled JDK applied, and then replace it with the required JDK.
1. Create a backup copy of the latest log files in the /var/logs/rainier-tool directory. If the problem persists after completing the rest of this procedure, contact customer support and provide these log files.
2. Remove and reinstall Ops Center Administrator.
3. Restore the settings using the rainier-backup-yyyymmdd-hhmmss.tar.gz file in /tmp. For details, see "Backing up and restoring system settings" in the Hitachi Ops Center Administrator User Guide.
4. Replace the JDK by manually running the rainier-replace-jdk command with the --keep-java option.
Note: If the problem persists, contact customer support. Provide them the latest log files in the /var/logs/rainier-tool directory, along with the backup copy of the log files created in Step 1.
If the installation produces any warnings or errors, they may point to the cause of the problem. Correct any issues the installer identifies, delete any Ops Center Administrator containers and images, and start the installation again.
If the problem persists after the issues are corrected, try a fresh installation.
1. Check that the backup file of the current version exists under the folder where install.sh is located and download the backup file.
  If the backup file does not exist, access the virtual appliance manager from the following URL, and download the backup file:
```
https://ip-address:port/vam
```
  where:
  - ip-address is the IP address of the Ops Center Administrator server.
  - port is the port number of the Ops Center Administrator. The default port number is 443 or 20961.
  The default login credentials are sysadmin/sysadmin
  - For an environment where the application installer version was originally installed, remove the older version and start a fresh installation.
  - For an environment where the preconfigured media installer version was originally installed, discard the current environment and perform a preconfigured media installation.
2. After the installation completes, apply the backup file.