Micro Focus seriously needs to look at the upgrade scripts in inplace OES2018SP1 updates. I'm currently busy doing lots of OES2015SP1 to OES2018SP1 updates, and the *vast* majoriy fails in oe way or the other, but every single time the core failure reason are the various service proxies, aka most of the time the common proxy, coupled with the lack of error handling in these scripts.
What I'm seeing:
1. DNS and DHCP if installed are disabled after the update. Trying to enable or manuall start them fails because they can't login to eDirectory to access their information.
Remedy: Often it is enough to run the "move_to_common_proxy.sh (which has it's own set of issues I posted about here: /collaboration/oes/f/oes_discussions/190966/move_to_common_proxy-sh-bug).
However, sometimes that doesn't fix it, in that case the common proxy repair script found here: /collaboration/oes/w/oes_tips/21913/common-proxy-repair-script-for-oes2018-oes2015-and-oes11
often helps. The issue seems to be that the common proxy password gets lost in the process somehow. When you manually attempt to reconfigure DNS or DHCP via Yast, you'll find that the Common Proxy password is empty and you can't proceed without it.
2. The upgrade hanging at "Saving Novell Cifs Services Configuration" forever. It will never recover from here. In the background, you can see Cifs trying to start over and over once per minute, but never susscesful. This must somehow be related to ncs, as in Y2log the last activity shown was:
[Ruby] modules/NovellUtils.rb:2145 Moving novell-ncs service to common proxy
The only way (I have found) out of here is to forcefull kill all y2start threads, and then manually fix the common proxy (again). Here only the common proxy repair script as per above helps.
Needless to say that all services were working flawlessly before the upgrade, and the common proxy was set for all of them (e.g, running the "move_to_common_proxy.sh" script before the update stated that nothing needs to be done".