BuildMaster: upgrade 22+ failed on OpenShift

[marc.ledent_9164]

Hi all,

We have a running Buildmaster v 7.0.23 on OpenShift that we want to upgrade to the last version (24.0.x)

Upgrading to 7.0.25 is working. But when I want to upgrade to 22.x or higher, I cannot access to the app: err 504: gateway timeout. A curl inside the container gives the same result.

I already had a look at the thread "[ProGet] Manual database upgrade (docker, kubernetes)", but the solution is using the arg "upgrade" of ProGet that is not existing for BuildMaster.

What hint do you suggest me to solve this problem?

Thanks in advance,
Marc

[atripp]

Hi @marc-ledent_9164 ,

I'm guessing that, if you're getting that error, it probably means that the BuildMaster service is somehow crashing on start-up and thus not running.

If this is the case, you should see some kidn of error message in the service (container) console output logs.

I don't know enough about OpenShift to advise how to find these logs, but if you can just do the equivalent of docker run without -d (detached) then the console output will be streamed to the console, and you can see the error messages.

Cheers,
Alana

[marc.ledent_9164]

I already checked the console an didn't see anything bad, except those lines:

Unable to auto-activate license. Error was: The request was canceled due to the configured HttpClient.Timeout of 100 seconds elapsing.
Unable to auto-activate license. Error was: The request was canceled due to the configured HttpClient.Timeout of 100 seconds elapsing.
info: Microsoft.AspNetCore.Hosting.Diagnostics[2]
Request finished HTTP/1.1 GET http://mdw-deploy-bima-alpha.apps.gcloud-04.paas.services.gcloud.belgium.be/ - 302 0 - 100320.3875ms

As we do not have connection to the internet, even by proxy, those messages should be considered as "normal"

What is strange, is that we have listeners on ports, but a curl on those ports are failing in timeout...

Marc

[atripp]

Hi @marc-ledent_9164 ,

I'm not really sure how to debug OpenShift/Kubernetes, so I really don't even know what to suggest to look at. This may also be unrelated to the platform at all, but we just aren't seeing the real error. Ultimately I do think the web service isn't starting, which makes it really hard to see errors.

There is a database table in BuildMaster that might contain some iinformation (LogMessages); it should be prety obvious which message it is.

Another thing you could/should try is a fresh, Docker-only installation of BuildMaster 2024. That should "just work" out of the box. Then bring to OpenShift/Kube. if that works, we at least know it's some kind of configuration delta.

BuildMaster 7 was our first Linux edition, so it's possible there was some configuration that worked on that, but not in newer. But we just need a starting point/error.

Hopefully the error table has some info

Thanks,
Alana

[marc.ledent_9164]

Hi @atripp ,

Thanks for the suggestions. Concerning the LogMessages table, we already have those messages displayed on the OpenShift console, but nothing suspect can be seen.

What I'll try is to test a fresh install of the last BuildMaster version and see what difference we have with our "updated" version.

I'll keep you in touch.
Marc