Most likely this is a problem with AM upgrade assistant registering additional repos/products.

I would try first this (changing baseproduct to SLES.prod):

https://www.microfocus.com/documentation/access-manager/5.0/install_upgrade/t4g8iefojgah.html

And it his is not enough, also this (temporary removing am.prod):

https://portal.microfocus.com/s/article/KM000006432?language=en_US

Kind regards,

Sebastijan

Unfortunately none of that helped.  The base product symlink was already correctly pointing at the SLES product file.  I did try moving am.prod out of the products.d directory, but that made no difference either.  I was hoping this was the key, but I guess not.  Have you actually upgraded a NAM 5 box from SLES 12 to 15?  I wonder if it is even possible?  I've done none-NAM servers many times without incident.

I typically don't use the Upgrade Assistant, I find that it was very poorly thought out and implemented and is generally more trouble than it is worth. I'm typically more aggressive with OS patching and much more cautious with NAM patching, especially with the poor quality of the last few SPs.  This makes it hard to do just the OS updates (especially on the AG appliance).  Better off just skipping the Upgrade Assistant altogether and sticking to the tarball install.

Oh, one correction from my previous post. I found that while my in-place upgrades of RHEL 7.9 to 8.8 worked for the admin console and the identity server, the gateway service did not work (I thought it had).  There is an SSL library problem, but that is probably because RHEL 8.8 is not supported.  I'll have to test going to an earlier version of RHEL.

Matt

I've been doing more extensive testing in my lab, building SLES 12 SP5 VMs, installing NAM 5.0, and trying to do in-place upgrades.  From what I can tell, it is IMPOSSIBLE to in-place upgrade a SLES 12 SP5 server with NAM 5.0 installed to SLES 15 SP4.  I have yet to find a way to do it.  NAM 5.0 appears to do something with the product registration on the box that causes the SLES 15 SP4 upgrader to be unable to figure out a migration plan for the server, resulting in an upgrade failure.  If I role back the exact same VM to the base SLES 12 SP5 VM BEFORE NAM 5.0 was installed, the in-place upgrade works perfectly.  I think this is a major issue.  I opened a support case on it, but that has been a futile effort so far.

With SLES 12 SP5 nearing end-of-life I was kinda hoping this would be an option, at least on the admin console which is difficult to move (rebuilding identity servers and gateways isn't that bad).

Matt