5.6 Channel Upgrade from OES 2018 SP2 to OES 2018 SP3

IMPORTANT:Stop OES Cluster service (NCS) on the node that is getting upgraded before proceeding with Channel Upgrade.

5.6.1 Channel Upgrade from OES 2018 SP2 to OES 2018 SP3 Via Wagon

  1. Register the OES 2018 SP2 server with NCC using the following command:

    suse_register -a email=<Email-Address> -a regcode-oes=<OES-activation-key> -L /root/.suse_register.log

  2. Run the zypper lr command to ensure that OES2018-SP2-Pool, OES2018-SP2-Updates, OES2018-SP2-SLES12-SP5-Pool, OES2018-SP2-SLES12-SP5-Updates, OES2018-SP2-SLEModule-Containers12-Pool, and OES2018-SP2-SLEModule-Containers12-Updates catalogs are subscribed and enabled.

  3. Apply all the available patches either using zypper update -t patch or yast2 online_update. In the list of available patches, ensure that the Enable update to OES 2018 SP3 is selected. If this patch is not installed, you cannot proceed with the upgrade.

    NOTE:If the patching requires a server reboot, do so when notified by the system.

  4. Start the wagon upgrade module using the yast2 wagon command.

  5. On the welcome screen, click Next.

  6. In Registration Check screen, click Run Registration if the “System not Registered” warning is displayed.

  7. The Run Registration redirects to the NCC screen and click Next. Wagon does a sync and pops up a message stating that the software repositories need not be changed. This happens as there are no updates at this stage.

  8. In the Registration Check screen, ensure that the registration summary displays “Open Enterprise Server 2018 SP2has a valid registration”. If the valid registration message is displayed, click Next, and it resets the package manager.

  9. In the Update Method screen, select Customer Center > Next.

  10. The NCC screen is displayed again. Click Next, and it does a sync and pops up a message stating that the configuration is successful. Click Details and ensure that the following repositories are enabled as shown in the following figure.

    NOTE:If the repositories are not enabled, click Back > Next and redo the NCC registration until it is successful. If you are not able to do a successful NCC registration after multiple attempts, abort the process and roll back the server. For more information, see Section 5.6.4, Rolling Back the Server in the Middle of a Wagon-based Channel Upgrade.

  11. In the Distribution Upgrade Settings screen, you must see the following content under the Update Options section.

    • Temporary migration product Open_Enterprise_Server Service Pack 3 Migration Product (Open_ Enterprise_Server-SP3-migration) will be removed

    • Product Micro Focus Open Enterprise Server 2018 SP2 (Open_Enterprise_Server) will be upgraded to Micro Focus Open Enterprise Server 2018 SP3 (Open_Enterprise_Server)

    WARNING:If Product Micro Focus Open Enterprise Server 2018 SP2 (Open_Enterprise_Server) will be upgraded to Micro Focus Open Enterprise Server 2018 SP3 (Open_Enterprise_Server) is not displayed, click Abort and roll back the server.

    NOTE:In the following screen shot, the number of packages to be updated may vary based on the patterns selected.

    IMPORTANT:After clicking Start Upgrade, you cannot revert the server to its old state.

  12. Click Next > Start upgrade and continue with the upgrade. Once the upgrade is complete, a pop up is displayed informing about a server reboot; click OK and continue with the upgrade.

  13. The NCC screen is displayed once again, wherein the registration of the final product is triggered. Click Next.

  14. At the final Migration Completed dialog, click Reboot to reboot the server and proceed with OES service configuration.

  15. After the reboot, system will prompt for eDirectory or DSFW password if the answer file is not created. Provide the password and continue. For more information on creating the answer file, see see Section 5.5.2, Creating an Answer File to Provide the eDirectory and DSfW Passwords.

  16. A Program Improvement screen is displayed if this is the first server that is upgrading to OES 2018 SP3. For more information, see Section 3.14, Product Improvement.

5.6.2 Channel Upgrade from OES 2018 SP2 to OES 2018 SP3 Using Zypper

  1. Register the OES 2018 SP2 server with NCC using the suse_register -a email=<Email-Address> -a regcode-oes=<OES-activation-key> -L /root/.suse_register.log command.

  2. Run the zypper lr command to ensure that OES2018-SP2-Pool, OES2018-SP2-Updates, OES2018-SP2-SLES12-SP5-Pool, OES2018-SP2-SLES12-SP5-Updates, OES2018-SP2-SLE-Module-Containers12-Pool, and OES2018-SP2-SLE-Module-Containers12-Updates catalogs are subscribed and enabled.

  3. Run the zypper update -t patch command to install package management updates.

  4. Run the zypper update -t patch command once again to install all the available updates for OES 2018 SP2. Ensure that the Enable update to OES 2018 SP3 patch is installed. If this patch is not installed, you cannot proceed with the upgrade.

    NOTE:If the patching requires a server reboot, do so when intimated by the system.

  5. Run the zypper pd command to ensure that the Open_Enterprise_Server-SP3-migration is listed but not installed. To check the products installed, run zypper pd -i command.

  6. The installed products contain information about the distribution upgrades and the migration products that should be installed to perform the migration. Use the zypper se -t product | grep -h -- "-migration" | cut -d\| -f2 command.

    A sample output is as follows:

    Open_Enterprise_Server-SP3-migration

  7. Install these migration products using the zypper in -t product Open_Enterprise_Server-SP3-migration command.

  8. Run the suse_register -L /root/.suse_register.log command to register the products and to get the corresponding repositories.

  9. Run the zypper ref -s command to refresh services and repositories.

  10. Check the repositories using the zypper lr command. It should list OES2018-SP3-Pool, OES2018-SP3-Updates, OES2018-SP3-SLES12-SP5-Pool, OES2018-SP3-SLES12-SP5-Updates, OES2018-SP3-SLE-Module-Containers12-Pool, and OES2018-SP3-SLE-Module-Containers12-Updates repositories, and they should be enabled.

  11. Perform a distribution upgrade using the zypper dup --from OES2018-SP3-SLES12-SP5-Pool --from OES2018-SP3-SLES12-SP5-Updates --from OES2018-SP3-Pool --from OES2018-SP3-Updates --from OES2018-SP3-SLE-Module-Containers12-Pool --from OES2018-SP3-SLE-Module-Containers12-Updates command.

    • The following product is going to be REMOVED:

      Open_Enterprise_Server Service Pack 3 Migration Product

      REMARK: You can choose to ignore this message. The actual product that is being removed is OES 2018 SP3 Migration Product.

      The following product is going to be upgraded:

      MicroFocus Open Enterprise Server 2018 SP3 2018.2-0 -> 2018.3-0

      It’s safe to ignore the following messages as well. They have no impact on the channel upgrade.

    • The following packages are going to be downgraded:

      gnome-shell-extensions-common-lang iscsiuio libdbus-1-3 libdbus-1-3-32bit libopeniscsiusr0_2_0 libxatracker2 libyui-ncurses-pkg7 libyui-qt-pkg7 microfocus-libconfuse0 novell-ad-util novell-afp-nmasmethods novell-afptcpd novell-afptcpd-interfaces novell-cifs novell-cifs-interfaces novell-cifs-nmas-methods novell-client-script novell-dnsdhcp-javaconsole novell-filesystem novell-imanager-filesystem

      NOTE:The packages listed here may vary based on your setup.

  12. Once the upgrade is successfully completed, register the new products once again using the suse_register -L /root/.suse_register.log command.

  13. Reboot the server.

  14. IMPORTANT: After the reboot, log on to the server and run the following command to complete the OES services reconfiguration:

    yast2 channel-upgrade-oes

    This will prompt for eDirectory or DSfW password if the answer file is not created. Provide the password and continue. For more information on creating the answer file, see Section 5.5.2, Creating an Answer File to Provide the eDirectory and DSfW Passwords.

5.6.3 Upgrading OES 2018 SP2 to OES 2018 SP3 By Using Micro Focus Subscription Management Tool

  1. Install and set up the Micro Focus Subscription Management Tool (SMT) server. For more information on setting up SMT, see Micro Focus Subscription Management Tool.

    NOTE:Ensure to use Micro Focus SMT server for upgrading to OES. Because SMT on SLES 12 cannot access and mirror the OES update channels hosted on NCC.

  2. Mirror down the following channels on to the SMT server:

    • OES 2018 SP3: OES2018-SP3-Pool, OES2018-SP3-Updates, OES2018-SP3-SLES12-SP5-Pool, OES2018-SP3-SLES12-SP5-Updates, OES2018-SP3-SLE-Module-Containers12-Pool, and OES2018-SP3-SLE-Module-Containers12-Updates channels

    • OES 2018 SP2: OES2018-SP2-Pool, OES2018-SP2-Updates, OES2018-SP2-SLES12-SP5-Pool, OES2018-SP2-SLES12-SP5-Updates, OES2018-SP2-SLE-Module-Containers12-Pool, and OES2018-SP2-SLE-Module-Containers12-Updates channels

    For more information on Mirroring and Managing the repositories, see Mirroring Repositories on the Micro Focus SMT Server and Managing Repositories with YaST Micro Focus SMT Server Management.

  3. Register the OES 2018 SP2 server with the SMT server. For more information on registering, see Configuring Clients with the clientSetup4SMT.sh Script in the Micro Focus Subscription Management Tool Guide.

  4. After registration, upgrading the OES 2018 SP2 to OES 2018 SP3 is the same as that of NCC upgrades as described from Step 2 in Section 5.6, Channel Upgrade from OES 2018 SP2 to OES 2018 SP3.

    NOTE:If you use Wagon and SMT based upgrade, you will not go through the Step 6 to Step 8 mentioned in Section 5.6.1, Channel Upgrade from OES 2018 SP2 to OES 2018 SP3 Via Wagon. After clicking on next in Step 5 continue from Step 9.

5.6.4 Rolling Back the Server in the Middle of a Wagon-based Channel Upgrade

After multiple failed attempts to do an NCC registration, follow this procedure to roll back the server to its previous state safely.

  1. Click Abort > Abort Installation.

  2. In the Reverting Migration screen, click Next.

    IMPORTANT:Do not click Abort in this screen as it will abort the revert process.

  3. In NCC registration screen, click Next.

  4. Follow the screen prompts and complete the revert process.