This is just one possible scenario which I still think worth documenting and sharing as the documentation on the upgrade paths and pitfalls from MicroFocus is not abundant to say the least. Pretty much all one can find by a direct Google search for "oes2015 to oes2018" are seven (7) links as of 04/19/2019 of which the following are of most interest in my opinion:

https://www.novell.com/documentation...aths_2018.html

https://support.microfocus.com/kb/doc.php?id=7023130

https://ohmag.net/?p=2376

After reading all of the above and having had a support case opened with MicroFocus, which pretty much assured me everything should go smoothly with minor issues related to upgrading Apache from v2.2. to 2.4, I went ahead with the upgrade and ran into quite serious issues.

Here it goes.

Environment

GW14.2 on OES2015 SP1 with the latest patches applied running on ESXi 5.5, (9919047), VM HW version 8, NIC VMXNET3, NSS locally attached storage used for GW data

Challenge

Perform the in-place upgrade of the OS and of the GW

Steps

1. Upgraded GW 14.2 to GW 18.1 with no issues
2. Started OES 18.1 Upgrade, received a warning the partitions were referenced by IDs, aborted the installation, booted back into OES2015, changed partition references in the FSTAB and in the Boot Loader to labels (by-label) using Partitioner and Boot Loader applications in YaST
3. Tested reboot in OES2015
4. Re-started the OES2018 upgrade
5. The upgrade stuck on the eDirectory upgrade phase. Specifically, it was complaining of its inability to synchronize time with the writable NDS replica holder, and of the admin authentication failure with "...error: 0" Error message related to the time synchronization issue showed a truncated time server FQDN
6. Made sure time synchronization was working fine from both ends. Ran DSREPAIR on NetWare, no issues
7. Changed credentials format (Validation succeeded) to no avail
8. Identified Apache was not starting. Repaired in a SSH session by partially following https://support.microfocus.com/kb/doc.php?id=7023130 Please note, in the Resolution, part 3, paths are inaccurate, link syntax is incorrect. I opted to using MC to modify the paths respectively. Apache still did not start as OES2018 dropped iFolder support, so all iFolder and MONO configs (folder* and simian) needed to be removed from /etc/apache2/conf.d All other configs needed to be modified as the "Order allow, deny" construct was deprecated in Apache 2.4 Used https://httpd.apache.org/docs/2.4/upgrading.html as a reference. Apache started, still no fun. Specifically GroupWise failed to start
9. Aborted the installation
10. Determined NSS storage was not mounted. For example, _admin was blank which would not also nss or nssmu to execute
11. Logged in as root in SSH and ran YaST there. Went to Open Enterprise Server / OES Install and Configuration. Re-ran the upgrade process which did not complain of any time or authentication issues, and eventually succeeded. Please note, iManager installation takes particularly long time
12. Verified NSS storage mounted. GroupWise started

Conclusion

There are bugs in the GUI based upgrade script