2.1 OES Installation, Upgrade and Update

2.1.1 Package Conflict Issue

During the OES upgrade, you may encounter package conflict issues related to PHP version 8. To resolve this issue, you must uninstall PHP version 7 and then proceed with the OES upgrade.

2.1.2 Channel Upgrade Issue

The value of "SERVICE_CONFIGURED=" in /etc/sysconfig/novell/edir is changed from "yes" to "no" by the "yast2 channel-upgrade-oes" command during the Channel Upgrade from OES 2023 to OES 23.4 using Zypper. This was resulting in an upgrade issue, which is now fixed in Update 5.1 OES 2023 Hotfix.

To avoid this issue, ensure that OES 2023 is updated with the latest patches from the channel before upgrading to OES 23.4.

2.1.3 Upgrade Issue in SUSE Xen Hypervisor Environment

If you are in a SUSE Xen Hypervisor environment and upgrading to OES 23.4, the upgrade fails. It is recommended to follow either one of the following workarounds:

  • If you have already registered to customer center, you must Cancel the xen-tools-domU package installation to proceed with the upgrade process.

  • If you have not registered to customer center, skip the registration to proceed with the upgrade process.

2.1.4 NCS and Upgrade Issue

When OES Cluster Services (NCS) and Business Continuity Clustering (BCC) are upgraded from OES 2023 to OES 23.4, NCS and BCC are not configured after the upgrade, hence NCS cluster and BCC peer clusters are not visible in the cluster view.

To resolve this issue, you must modify the administrator credentials or LDAP server settings that you assigned when you created the cluster. See, Changing the Administrator Credentials or LDAP Server IP Addresses for a Cluster in OES 23.4: OES Cluster Services for Linux Administration Guide.

2.1.5 OES Server Registration to MFSMT Fails

The registration of OES server to MFSMT fails with ERROR: 500: Server error!. This is because the SMT server is unable to identify the client IP address.

To avoid this issue, perform the following on the SMT Server:

  1. Go to the file /srv/www/perl-lib/SMT/Registration.pm.

  2. At line number 714, replace $hostname = $r->connection()->remote_ip(); with $hostname = $r->connection()->client_ip(); and save the file.

  3. Restart the Apache service by using the command systemctl restart apache2.service.