Open Enterprise Server (OES) product/s missing

[CSGRhysHa]

Problem description

When using OpenText mirror / SMT login credentials in 'organization credentials' all of my SUSE SLES products are shown except any OES products (Versions 12 to 24.4).
It seems only SUSE products are being found by Uyuni even though the mirror credentials are from my OpenText account.

Steps to reproduce

1. Install Uyuni 2024.12 on fresh openSUSE Leap Micro 5.5
2. Add OpenText mirror / SMT credentials
3. Wait for products to refresh
4. See that no OES products are listed

Uyuni version

2024.12-241000.225.1.uyuni5

Uyuni proxy version (if used)

Useful logs

Found this error in /var/log/rhn/rhn_web_ui.log when clicking the "list subscriptions" on the credentials.

2025-02-02 19:16:48,348 [ajp-nio-0:0:0:0:0:0:0:1-8009-exec-1] ERROR com.redhat.rhn.frontend.servlets.SessionFilter - Error during transaction. Rolling back
java.lang.NullPointerException: Cannot invoke "java.lang.Long.longValue()" because "id" is null
        at com.redhat.rhn.frontend.action.renderers.setupwizard.MirrorCredentialsRenderer.listSubscriptions(MirrorCredentialsRenderer.java:219) ~[rhn.jar:?]
        at com.redhat.rhn.frontend.servlets.ajax.AjaxHandlerServlet.lambda$static$4(AjaxHandlerServlet.java:129) ~[rhn.jar:?]
        at com.redhat.rhn.frontend.servlets.ajax.AjaxHandlerServlet.doPost(AjaxHandlerServlet.java:176) ~[rhn.jar:?]
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:555) ~[tomcat-servlet-4.0-api.jar:4.0.FR]
        at javax.servlet.http.HttpServlet.service(HttpServlet.java:623) ~[tomcat-servlet-4.0-api.jar:4.0.FR]
        at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:199) ~[catalina.jar:9.0.97]
        at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:144) ~[catalina.jar:9.0.97]
        at org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:51) ~[tomcat-websocket.jar:9.0.97]
        at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:168) ~[catalina.jar:9.0.97]
        at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:144) ~[catalina.jar:9.0.97]
        at com.opensymphony.module.sitemesh.filter.PageFilter.doFilter(PageFilter.java:45) ~[sitemesh.jar:?]
        at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:168) ~[catalina.jar:9.0.97]
        at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:144) ~[catalina.jar:9.0.97]
        at com.redhat.rhn.frontend.servlets.LocalizedEnvironmentFilter.doFilter(LocalizedEnvironmentFilter.java:71) ~[rhn.jar:?]
        at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:168) ~[catalina.jar:9.0.97]
        at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:144) ~[catalina.jar:9.0.97]
        at com.redhat.rhn.frontend.servlets.EnvironmentFilter.doFilter(EnvironmentFilter.java:99) ~[rhn.jar:?]
        at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:168) ~[catalina.jar:9.0.97]
        at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:144) ~[catalina.jar:9.0.97]
        at com.redhat.rhn.frontend.servlets.SessionFilter.doFilter(SessionFilter.java:59) ~[rhn.jar:?]
        at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:168) ~[catalina.jar:9.0.97]
        at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:144) ~[catalina.jar:9.0.97]
        at com.redhat.rhn.frontend.servlets.SetCharacterEncodingFilter.doFilter(SetCharacterEncodingFilter.java:98) ~[rhn.jar:?]
        at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:168) ~[catalina.jar:9.0.97]
        at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:144) ~[catalina.jar:9.0.97]
        at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:168) ~[catalina.jar:9.0.97]
        at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:90) ~[catalina.jar:9.0.97]
        at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:482) ~[catalina.jar:9.0.97]
        at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:130) ~[catalina.jar:9.0.97]
        at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:93) ~[catalina.jar:9.0.97]
        at org.apache.catalina.valves.AbstractAccessLogValve.invoke(AbstractAccessLogValve.java:660) ~[catalina.jar:9.0.97]
        at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:74) ~[catalina.jar:9.0.97]
        at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:346) ~[catalina.jar:9.0.97]
        at org.apache.coyote.ajp.AjpProcessor.service(AjpProcessor.java:424) ~[tomcat-coyote.jar:9.0.97]
        at org.apache.coyote.AbstractProcessorLight.process(AbstractProcessorLight.java:63) ~[tomcat-coyote.jar:9.0.97]
        at org.apache.coyote.AbstractProtocol$ConnectionHandler.process(AbstractProtocol.java:937) ~[tomcat-coyote.jar:9.0.97]
        at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1791) ~[tomcat-coyote.jar:9.0.97]
        at org.apache.tomcat.util.net.SocketProcessorBase.run(SocketProcessorBase.java:52) ~[tomcat-coyote.jar:9.0.97]
        at org.apache.tomcat.util.threads.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1190) ~[tomcat-util.jar:9.0.97]
        at org.apache.tomcat.util.threads.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:659) ~[tomcat-util.jar:9.0.97]
        at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:63) ~[tomcat-util.jar:9.0.97]
        at java.lang.Thread.run(Thread.java:840) ~[?:?]

Additional information

I've only noticed this in 2024.12 so not sure if the issue existed in previous versions.

[alex-in-it]

We have also seen this issue appear recently. We have yet to migrate to the containerised Uyuni, so we are on version 2024.08 still. We were considering upgrading to see if it fixed the issue, but given this report, we will continue to hold fire.
If it helps, from the reposync logs on our Uyuni, this seems to have broken around the 13th of January. The reposync logs don't report errors, just that "the repo URL is empty".
We only noticed when we went to see if OES 24.4 was available to mirror.

[mackdk]

We are currently looking into this issue and trying to understand what's going on. I'll update the card when we have more details.

[lucidd]

this sounds like its related to the fix we just merged here #9824. It should be in the next uyuni update

[CSGRhysHa]

Is there a way I can test this fix on a non-prod Uyuni install?

[alex-in-it]

Thanks guys. If CSGRhysHa has success with the fix, I will push to get ours upgraded to latest.

[juliogonzalez]

Is there a way I can test this fix on a non-prod Uyuni install?

@CSGRhysHa yes, you can deploy a development Uyuni Server: https://www.uyuni-project.org/pages/devel-version.html

Please do not use such as a deployment for production. Such environments can be updated to Stable later, and updates even from deployment to deployment do not work.

Thanks guys. If CSGRhysHa has success with the fix, I will push to get ours upgraded to latest.

@alex-in-it be aware the current released version does not include the fix yet. So even if @CSGRhysHa is able to test using development, we need to release the next version (probably 2025.03) to get the fix released.

[alex-in-it]

@juliogonzalez Thanks for the heads up. I can let our team know that we need to hang in for the next release. In case you know, will we be able to migrate from 2024.08 straight into that version? I already know that it will be a new containerised server regardless.

[juliogonzalez]

@juliogonzalez Thanks for the heads up. I can let our team know that we need to hang in for the next release. In case you know, will we be able to migrate from 2024.08 straight into that version? I already know that it will be a new containerised server regardless.

It should work. The procedure for the server and equivalent for the proxy should work just fine.

But as always, keep an eye on the release notes, of course :-)