OES2018sp1 Upgrade via local smt registration?

[mrosen]

Hi.

For the life of me, I can't get this to work, in various environments. When I try to register a OES2018SP1 (Rev.A) server while upgrading against a local SMT server, I always get a "registration failed" error, and the details show a "404 Error". Of course, registering the server after the upgrade against the same SMT works fine and applies all repos and the server can be patched.

What am I missing? I'd really like to apply patches during the upgrade due to some bugs in the upgrade scripts themself have been fixed since release....

[mathiasbraun]

Upgrading from OES2015SP1?

[mrosen]

---

@mathiasbraun wrote:

Upgrading from OES2015SP1?

---

Yes, but I strongly assume the source OS would make no difference at that point. I also assume it would fail even when doing a fresh install and trying to register that to the SMT while installing.

[mathiasbraun]

As a quickshot i've just tried a fresh install and could register against my local smt without issues. I went though the "network configuration" dialog (static setup) before entering smt details, maybe the order makes a difference...

[mrosen]

Thanks for checking. Of course, I have to try this with a fresh install now too, just in case it really only happens when updating.

Other than that, I'm stumped, because I can dupe it in three completely separate environments, and have yet to see it work anywhere.

Oh, I too went though the static network setup. After all, it *does* contact the SMT server (including offering thr certificate proper and storing it). If it couldn't connect, it couldn't receive a 404 error after all. 😉

[mathiasbraun]

Shouldn't the 404 get logged in the SMT's access_log along with the corresponding GET?

[mrosen]

Sorry, yes.

[12/Nov/2019:22:47:39 +0100] "POST /?command=listproducts&lang=en-US&version=1.0 HTTP/1.1" 404 -

That seems to be the one.

[mathiasbraun · Accepted solution]

Did you append the "/center/regsvc" part to the SMT server definition? Just because my logs don't contain any failed attempt and all entries containing "listproducts" look like

"POST /center/regsvc?command=listproducts&lang=en-US&version=1.0 HTTP/1.1"

My logs reach back 'til Jan2019, but i'm pretty sure i had a few upgrades to 2018 since then.

[davidkrotil]

It´s SLES12, but OES, than you need use NCC SMT with folder part as @mathiasbraun is saying.

[mrosen]

---

@mathiasbraun wrote:

Did you append the "/center/regsvc" part to the SMT server definition? 

That went "woosh" over my head. Can you elaborate what you mean?

P.S: Got it. Wen specifiying the local registration server during the OES2018 Upgrade, one must specify https://smtserver.yourdomain.com/center/regsvc

Just the servername doesn't do it.