In the normal case on a Unix system, user.Current is just returning what getpwuid_r returns. If you call getpwuid_r when there is no user ID, it will return NULL, and so user.Current returns a value of type user.UnknownUserIdError.

I guess the argument for doing something different would be that if the program is built with CGO_ENABLED=0, then user.Current tries to work out a user.User value based on the environment variables USER and HOME. If those environment variables are found, the function succeeds.

So, on the one hand, presumably C programs that rely on getpwuid_r also fail on Openshift. On the other hand, user.Current does try to work without additional information in some cases. I see an argument both ways.

Why is your Go program calling user.Current? Does Openshift provide USER and HOME environment variables?

There is a userid, it's just not set in the passwd file.
The software I'm actually using does not seem to do other than getting the username and home.
I'll try and compile it myself with CGO_ENABLED=0.
I'll also open an issue on Jobber's git page.
I'm closing the issue, as it is not a bug. Thank you @ianlancetaylor for pointing me to the right direction.
I also think programs that rely on getpwuid_r fail on Openshift infrastructure. But not every program is meant to run there, openshift is mostly for webservices and databases.
Jobber was kind of "good to run" too because it's a "cron like" program with better output.